Overview
It's crucial to distinguish between actions initiated by managers and employees, particularly concerning compliance, consent, and premium pay. This distinction impacts issues such as forgotten punches or input errors.
The accompanying video demonstrates examples within a compliance context:
Manager-initiated actions that result in premium pay.
Employee-initiated actions that do not result in premium pay.
Any adjustments made by a manager will trigger a notification to the employee. Depending on the settings, this notification serves as a consent framework, requiring the employee to either agree to or acknowledge the changes, ensuring they are aware of the modifications.
Remember: Manager-initiated edits are the ones to watch for compliance and premium pay — they trigger an employee notification and, depending on settings, require the employee's consent. Employee-initiated actions typically don't.
Managers Editing Their Own Punches (May 2026)
As of May 2026, a new per-manager toggle lets designated managers (Shift Manager role and above) create and edit their own time punches directly in Timekeeping. Previously, this required using a physical time clock or having a blanket "approve own punches" setting enabled.
Mandatory Comment When Consent Workflow Is Not Used (July 2026)
As of July 2026, for businesses that do not use the time-punch consent workflow, managers must now enter a comment when editing an employee's time punch. This comment is sent to the employee and logged in the punch history.
Features in these release notes may not apply to all clients. Availability depends on your product version, subscription plan, and system configuration. Contact support for details.
