Review missing clock-outs before attendance reaches payroll

A missing clock-out should stay visible as an unresolved attendance record, not become an assumed departure time. Give the employee a correction route and show the payroll team which records still need a decision before export.

Odoo 18, for example, flags a check-in left open beyond 24 hours or a single attendance period longer than 16 hours.[1] Those are product-specific thresholds. Agree your own exception rules before development rather than copying them without review.

Keep the original event and the correction

Store the captured check-in separately from any proposed check-out. A correction should carry its reason and supporting information, with the original event still available to an authorized reviewer.

OWASP distinguishes event time from logging time, including records from intermittently connected devices.[2] For attendance imports, retain the device event time and receipt time separately when available. A late upload should not look like a new arrival just because the server received it later.

Record who requested and approved a correction, when the decision happened and what changed. Restrict approval to the responsible reviewer. Odoo 18 limits non-administrator approvers to attendance records for their assigned employees.[1] Define equivalent boundaries for your application; a correction form should not grant access to everyone else's attendance.

Make automatic closure explicit

Odoo 18 can automatically check employees out according to their working schedule after a configured buffer.[1] If your system uses a similar rule, label that closure as automatic. Keep it distinguishable from a clock-out captured at a kiosk or in an app.

Submitting a correction request should not make the record appear approved. Show the employee whether the request reached the server, whether review is pending and what to do if submission failed. W3C's form guidance calls for feedback on successful and unsuccessful submissions.[3] Keep those messages separate from the review outcome.

Show unresolved records to payroll with their review status rather than silently substituting scheduled hours. The employer and its payroll adviser decide how those exceptions are handled.

Test the awkward cases before sign-off

Use an overnight shift as well as a forgotten departure. Check a clock-out uploaded after a correction has already been approved, and a request the reviewer rejects. Verify that the original events, proposed changes and decisions remain distinguishable in the employee view, reviewer history and export.

Rootscratch's HR & Payroll System Development scope can include attendance imports, payroll previews, adjustments and finance exports.[4] Start with your attendance sources, review owners and a small set of exception records. Your payroll or finance adviser must validate statutory calculations and filing outputs; a custom system is not automatically compliant.[4]

Sources

[1] https://www.odoo.com/documentation/18.0/applications/hr/attendances.html — Odoo 18: attendance errors, automatic check-out and approver access [2] https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html — OWASP: application event logging and timestamp provenance [3] https://www.w3.org/WAI/tutorials/forms/notifications — W3C WAI: clear feedback after form submission [4] https://rootscratch.com/services/hr-payroll-system — Rootscratch: HR & Payroll System Development