Attendance

Attendance management that accepts the way your team actually checks in

Bring biometric punches, USB attendance reports, approved missing-punch requests and remote attendance into one employee-day record.

What it does

How OPleo supports attendance.

OPleo matches attendance through the employee's stored biometric PIN or user ID. It merges check-in and check-out punches for a date, marks late arrival from the organisation's office start time, and keeps manual and device records visible together.

OPleo keeps the workflow connected without claiming to replace every specialist system. The focus is a dependable operational record that the right person can act on.

Built into OPleo

Features for attendance

01

Device and file ingestion

Use Cloud Push or ADMS devices, a local connector for legacy LAN devices, or import a supported ZKTeco USB report for historical data.

02

Employee PIN mapping

Only the biometric IDs saved on employee records become attendance records; unmatched device logs are reported without polluting payroll data.

03

Employee punch-correction requests

Employees can request missing check-in or check-out times for dates within the last 90 days. Requests follow the reporting approval chain; approved additions retain an approver and correction history.

04

Daily exceptions

Review present, late, absent, incomplete and leave records with the employee and date behind every result.

How the workflow holds together

Designed around the handoffs that create operational friction.

Each feature uses the organisation, employee and policy information already in the workspace. That reduces repeated entry and gives people the context they need before they decide or approve something.

1

Map people to the device

Enrol each person with a unique device ID and save the same value on their employee record.

2

Choose the connection path

Pair compatible Cloud Push devices, use a local connector for LAN-only hardware, or import a USB report.

3

Resolve missing punches

Employees submit missing-punch requests, and their reporting chain reviews additions before attendance is updated.

4

Review the daily record

Check missing, late, absent and leave records before payroll so the result reflects reviewed inputs.

A practical rollout

Put the shared record in place before asking it to drive decisions.

Start with the workflow and policy your team can validate. The aim is a reliable operational foundation, not a rushed migration of every old spreadsheet.

1

Identify the hardware path

Start by identifying whether each device supports Cloud Push or ADMS, needs a local connector on the office network, or will provide a USB export. Choose the path that matches the device rather than exposing a private device address to the public internet.

2

Map device IDs deliberately

Match each device user ID to the correct employee record before relying on attendance results. Unmatched logs remain visible for review instead of being silently attached to someone with a similar name.

3

Set the correction route

Confirm who reviews employee requests for missing check-in or check-out times. Approved requests add missing punches and retain their correction history; existing punches and approved leave are not changed by this request flow.

4

Use a daily exception review

Review incomplete, late, absent, leave and manual records before payroll. This keeps attendance correction close to the day that occurred and gives payroll a clearer, traceable input.

What to validate

Clear inputs and ownership make the workflow dependable.

  • OPleo stores device user IDs and attendance punches; it does not store fingerprint or face templates.
  • Legacy LAN-only devices require a connector within the office network rather than direct public exposure.
  • Attendance records require review when a device is offline, a punch is incomplete, or an employee has not yet been mapped.
  • Cross-midnight device pairing and downstream payroll treatment have not been validated end to end. Confirm the required work-date rule before rollout; next-day checkouts are flagged for payroll review and shift duration/overtime is not calculated from that date.

Questions teams ask

Questions about attendance

Can employees ask to fix a missing punch?

Yes. Employees can request a missing check-in or check-out for a date within the last 90 days. The request follows the reporting approval chain, and an approved addition is recorded in attendance with correction history.

Does OPleo support shifts that cross midnight?

An employee correction or supported import can retain an explicitly supplied next-day check-out date, and payroll review flags those records. Device punch pairing and the downstream payroll treatment have not been validated end to end, so confirm the work-date rule and test your actual device data before relying on this workflow.

Can manual attendance coexist with biometric data?

Yes. Both resolve to the same employee-day record, preventing duplicate days.

How is late attendance decided?

The late threshold comes from that organisation's configured office start time.

Try a calculation

A practical tool for your next review

Calculate attendance percentage. See the formula and assumptions before using the result.

Review late-arrival records

Estimate time above the grace allowance

Use reviewed attendance figures in the late-arrival deduction calculator for a user-supplied planning estimate. This is not an OPleo deduction or a decision about whether a deduction is permitted.

See how OPleo fits the way your team already operates.

Request a demo