Receiving a punch from a device is the easy part. The real system begins with shifts, time zones, missed punches, meal rules, corrections, leave, privacy, and review.
Inspect original time and adjustment ownership fields.
Keep an ignore decision separate from a manual time correction.
Review the audit columns for old/new time, action and reason; this event has no edits.
Actual Pro-A-Motors interface captures. Private identities and contact details are covered or outside the crop; screen data has not been replaced.
What improved
Connect a timecard correction to its original event.
The business problem
A timestamp from a scanner is not yet trustworthy attendance. This workflow was created to preserve the source event while adding the time, device, correction, and review context needed for payroll work.
What we changed
Original scanner events remain available beside device, time and correction context for attendance review.
What the team can do now
Employees and supervisors can understand what happened, correct what needs attention, and preserve the context behind the final attendance record.
Read the actual screen
A source event and a correction are separate records of work.
The inspected event is Punched. Its manual-adjustment area is empty and its Manual Edit Audit contains no rows.
Status
Punched
Manual adjustment
Not recorded
Audit
No edits on this event
Capture action
Read only
What the screen shows
The form exposes local and UTC labels, original punch time, adjustment ownership, an ignore flag and reason/note audit columns. This is interface evidence, not a timezone-conversion validation.
What the team does next
Investigate the source event before correcting attendance, and preserve the reason and old/new time when a correction is needed.
What the next team receives
The attendance administrator receives an explainable event rather than an unexplained overwritten timestamp.
How the work moves
Follow the work from one decision to the next.
01
Receive and normalize the event
Device, employee, local time, UTC time, and source status are recorded together.
02
Place it inside the workday
Shift boundaries, overnight rules, time off, and meal requirements determine how the event should be understood.
03
Surface what needs review
Missed punches, anomalies, overlaps, and manual adjustments reach the right supervisor.
04
Preserve the audit trail
Corrections and privacy-sensitive actions remain scoped, reviewable, and connected to their source.
Build notes and background
Data integrationWorkflow automation
Make the exceptions part of the workflow.
Keep the source event
Original-time and audit fields make a later correction explainable.
Ignoring and correcting are distinct
The form exposes separate treatment for excluding an event and changing its recorded time.
Protect employee context
Names and identifying device labels are covered here. The kiosk’s ID and PIN fields remain empty.
Existing records are shown as captured. Private identities are covered or outside the crop. No business records were changed for this collection. Implementation history supports behavior beyond the visible screen; a still image is not an end-to-end test or a measured productivity result.
Substantially extended from an existing commercial biometric integration and standard Odoo attendance, employee, and time-off foundations. Toro’s work is the operating workflow, safeguards, exception handling, and integration hardening described here.
