Attendance policy & manager approval
Two tabs that decide how attendance is judged and how leave and correction requests get approved.
Attendance policy
Settings → Attendance sets the rules Webelio uses when it reads a day. Most of these also live on each shift; this tab holds the org-wide defaults and the mobile controls.
| Setting | What it does |
|---|---|
| Grace period | Minutes of lateness Webelio forgives before a day is marked late. Set on the shift; a longer grace means fewer late marks. |
| Late-mark rule | When a check-in past the grace window counts as late. Late days can feed a late-deduction count at finalize. |
| Half-day threshold | The worked-hours mark below which a day becomes a half-day instead of a full present day. |
| Full-day threshold | The worked-hours mark at or above which a day is a full present day. |
| Location capture mode | Whether mobile check-in must carry GPS coordinates — off, on check-in, on check-out, or both. |
| Geofencing master switch | When on, a mobile punch must fall inside a branch's allowed area (its coordinates and radius) to be accepted. |
These rules apply to mobile check-in. Check-ins from the web, a biometric machine, or a manual mark by HR are never location-gated. The finer per-employee overrides live on the Attendance Permission page — set the org default here, override the exceptions there.
A branch that has no coordinates set fails open — everyone can check in there even with geofencing on. This is deliberate, so a half-configured branch can never lock out your staff. Add coordinates under Settings → Locations to make the fence real.
When someone can't check in, Webelio returns a plain reason — location required, outside the allowed area, or device not registered. The mobile check-in page explains each and how to fix it.
Overtime
Overtime pay is off by default. Two switches on this tab turn it on:
| Setting | What it does |
|---|---|
| Pay overtime | Turn on to pay for hours worked beyond the shift. Reveals the multiplier and thresholds below. |
| Overtime multiplier (×) | The rate for extra hours — e.g. 2× pays double. |
| Standard hours / day | The day length that extra hours are measured against. |
| Minimum overtime to count (min) | Ignore small overruns shorter than this. |
| Approve overtime before it's paid | On = employees request each extra day and only approved days are paid. Off = all extra hours are paid automatically. |
The overtime pay & approvals page covers the request-and-approve workflow in full.
Late-coming deduction
Turn on Deduct for late marks to cut pay for repeated late arrivals. Two fields set the policy:
| Setting | What it does |
|---|---|
| Free lates / month | How many late arrivals an employee gets each month before any deduction applies. |
| Day cut per extra late | The pay cut for each late beyond the free count — e.g. 0.5 is half a day's pay (maximum 1 day). |
The late/early threshold itself comes from the shift's grace period (Settings → Shifts); this policy only sets the pay penalty. The penalty appears on the payslip as its own Late deduction line — see payslips.
Manager Approval
Settings → Manager Approval decides whether the reporting manager reviews a request before it reaches HR.
It's one master switch plus a child toggle for each request type:
| Toggle | Covers |
|---|---|
| Master switch | Turns two-step approval on or off for the whole org. |
| Leave | Leave applications go to the manager first, then HR. |
| Reimbursement | Expense claims go to the manager first. |
| Attendance Regularization | Correction requests go to the manager first. |
| Overtime requests | Overtime pay requests go to the manager first, then HR. |
All are on by default. The routing applies only when the employee has a reporting manager set:
- Both switches on and a manager exists → the request starts with the manager (step 1), and their approval passes it to HR/Admin (step 2) for the final decision. An admin can't approve at step 1 — that's the manager's alone.
- Master switch off, no manager, or the child toggle off → the request goes straight to HR/Admin for a single decision.
Turn the master switch off if you're a small team where the owner approves everything anyway — every request then lands in one queue instead of two.
All requests, however they're routed, land in the unified Approvals queue.
What's next
- Mobile check-in — per-employee location controls and device binding
- Approving requests — clear the leave and regularization queue
- Settings map — jump to any other tab