A 30-minute walkthrough of the AutoTime 2.2 release, built almost entirely inside the application. See the new No Tax on Overtime engine, mandatory meal handling, faster timesheet corrections, and the calc-rule changes that shrink oversized rule sets.
Session Overview
This session focused on setup and configuration inside AutoTime, the reasoning behind each change, and the trade-offs to weigh when you turn a feature on. Below is a summary of the six features demonstrated, followed by talking points and timestamps so your team can jump to the part that applies to them.
The largest addition in 2.2. AutoTime now calculates, tracks, and exports the untaxed premium portion of overtime by pay week, using a dedicated accumulator and a new accume-analytics context. Year-to-date totals and a one-time backfill for prior periods are both supported.
FLSA-drivenMeal-penalty messaging now reads the same hours the post-process event uses. A reached-minimum-by-event-group option lets you group mandatory meal events and evaluate them against a set threshold, so PVE notifications match what actually posts.
California meal rulesSupervisors can replace an elapsed labor entry directly on the time card, the same way punch time already worked. No more deleting the entry, recreating it, and re-adding it just to move hours from indirect to direct.
Timesheet correctionsTwo changes cut down oversized rules: event groups summarize many attendance events in one row, and variables let you store a calculated value and reference it in later rules. Both work in the attendance and pay-rules contexts.
Easier to maintainA new message policy triggers a note to the employee and their manager when a time-off request posts as unpaid or partially paid because the balance was short. People find out before the pay stub, so it can be corrected inside the period.
Message policyYou can now enable or disable offline mode per terminal from the terminal profile. Limiting offline terminals reduces one-off configuration work and prevents the reconnect slowdown that happens when many terminals sync at once.
Terminal profileTalking Points
AutoTime looks at hours over 40 in a pay week and treats the premium portion as untaxed. If someone works 45 hours, 5 hours qualify. In the demo, Debbie Stone worked 46.05 hours, so 6.05 hours counted, priced at 50 percent of her rate for $30.25 in untaxed overtime.
Analytics rules run first to fill the untaxed OT accumulator. A second layer, accume analytics, reads from that accumulator to calculate hours, rate, and dollars, then rolls them into year-to-date totals. The premium rate is the average payroll rate times 0.5.
To capture overtime from earlier in the year, set a backfill range and run it a single time. Everything posted after that is picked up automatically by the untaxed OT analytics service. The export attaches to your existing payroll export as a sub-header or sub-trailer, so field order still has to match what payroll expects.
The old gap was that PVE validation only counted labor hours, so employees could get a meal-penalty notice the post-process later cleared. Grouping mandatory meal events and evaluating the group against a threshold, five hours in the example, keeps the notification and the posted result aligned.
Customers reported rules so large they were hard to maintain and hard to follow. Storing a summarized value in a variable and referencing it in the next rule breaks one giant equation into steps you can actually read and reuse across the attendance and pay-rules contexts.
Every offline-enabled terminal needs its own unique setup, and if 100 terminals all try to resync at once, the system can freeze. Naming one to three terminals for offline collection covers the outage without the reconnect bottleneck.
Jump to a Section
Update these timestamps to match your final YouTube upload. You can also paste them into the video description as chapter markers.
What the session covers and how to send questions during the demo.
Accumulators, accume analytics, process policy, and rule-set profiles.
Matching the payroll export, sub-header vs. sub-trailer, and the preview.
Event groups and PVE validation for California meal interpretations.
Correcting a time card without delete-and-recreate.
Event groups and variables to shrink oversized rules.
Two smaller additions to close the session.
How to submit a referral and earn maintenance credits.
Your services and support teams can help you configure and roll out any of these features. And if you know an aerospace or defense contractor who could use AutoTime, our referral program offers maintenance credits when a deal closes.
Copyright 2026 AutoTime Solutions. All rights reserved.