Deep attendance policy
Configure week-offs, thresholds, grace, late consequences, shortfall, swipe modes, punch rounding and work-date handling.
Apply configurable rules to punches, shifts and work patterns, explain why each day resolved as it did, and close exceptions before they become payroll corrections.
Resolve a 09:11 punch for an employee whose shift begins at 09:00.
Punch is one minute beyond grace
No payroll impact yetThird late mark becomes half day
Decision is explainable09:00–18:00 · 45-minute break
Work date: 29 Sep 2026Geo-fence: warn outside location
Policy preview availableUse this page as a product-evaluation path: start with the operating problem, inspect the representative interaction, then verify the exact policy and output in the live product.
Configure the module around your structures, policies, ownership and approval model—not a generic process diagram.
Configure week-offs, thresholds, grace, late consequences, shortfall, swipe modes, punch rounding and work-date handling.
Support web or mobile capture, geo-fence enforcement, batch upload, device registry and SFTP ingestion.
Handle fixed, flexible, rotational and midnight-crossing shifts with employee or group assignments.
Apply reason codes, limits, cut-offs and approval routes to missing punches and corrections.
Show why a day became present, late, half-day, absent or loss-of-pay instead of exposing only the result.
Simulate the resolved policy for an employee and date, then reprocess attendance after an authorised correction.
The exact screens differ by module, but the operating principle remains the same: the applicable rule, current owner, status, effective date and history stay visible.
These examples are illustrative product patterns grounded in the supported product material. Use the live product to validate the exact screen, policy and output required for your organisation.
See the rule, workforce scope and effective date before activation.
Use a representative employee, workforce group and effective date. Follow the transaction through owner, status and downstream impact.
Device data can be consumed, but biometric matching, facial recognition and buddy-punch detection are not presented as native capabilities.
The example measures below are illustrative. Definitions and thresholds should be configured around the operating cadence and evidence your team uses.
Configure attendance, leave, payroll, approvals, permissions and notifications around the way your organisation actually works, while keeping every policy scoped, dated and reviewable.
ExploreCreate shift patterns, publish rosters, manage changes and connect planned schedules to attendance, overtime and payroll.
ExploreConfigure eligibility, accrual, balance-year, sandwich, clubbing, carry-forward, comp-off and encashment rules for different employee populations through one policy resolver.
ExploreConnect effective-dated salary structures, attendance and leave inputs, earnings, deductions, reimbursements, recoveries and statutory calculations in a payroll run that can be reviewed and rolled back before finalisation.
ExploreUse your actual workforce groups, approval paths and edge cases during product evaluation.
Yes, supported source files or integrations can feed attendance data into duoHR. The platform does not currently claim to perform facial recognition or biometric matching itself.
The supplied product material describes both warn and reject enforcement, configurable for the relevant workforce and location policy.
Bring one representative workflow or current process challenge. The demo will show the operating path, controls and connected outcomes.