UZIO Product Updates, May 2025 - Part 1
In this release, we made several important improvements based on your feedback, designed to enhance accuracy, visibility, and efficiency across Payroll and Time Tracking workflows.
If you have any questions or feedback regarding these new features or improvements, please feel free to email us at support@uzio.com.
To learn more about our last release from Mar 2025, click here.
Quick Links
Improved Holiday Hours Distribution Logic
One-Time Deduction Override in Payroll Grid
New Work Location & Department Fields
Improved Holiday Hours Distribution Logic
In January, we introduced a new feature that allows you to create Customizable Holiday Policies, enabling you to:
- Define Paid or Unpaid Holidays
- Set Eligibility Criteria (e.g., Waiting Periods)
- Configure Premiums for Worked Hours
- Configure Custom Holiday Pay Rules
Following the January rollout, we received feedback regarding the calculation of holiday hours. Specifically, the system was reducing holiday hours equivalent to the hours worked, even when Holiday Premium Pay was set to NO, leading to payroll inconsistencies and confusion in time tracking records.
To address this, we've improved and updated the holiday hours distribution logic to fully align with the defined policy settings. This change ensures consistency between Time Tracking and Payroll and removes the need for manual corrections.
How It Works:
- Holiday Premium Paid = No
- Holiday hours are fixed based on standard policy and are not affected by whether the employee works on the holiday.
- Any hours worked on the holiday are treated as regular work hours and allocated to Regular, Overtime (OT), or Double Overtime (DOT) per existing rules.
- No Holiday Premium is applied.
- Holiday Premium Paid = Yes
- Hours worked on a holiday are classified as Holiday Premium Hours.
- If an employee works on a holiday, the corresponding holiday hours are reduced and transferred to Holiday Premium Hours.
- Unpaid Holiday Policy
- Holiday hours are always zero, regardless of hours worked or employee eligibility.
One-Time Deduction Override in Payroll Grid
Previously, deductions tied to a specific schedule (e.g., the first paycheck of the month) would not appear in special payroll runs. However, in specific cases, payroll admins needed to apply a custom deduction amount in a different paycheck. This required them to temporarily adjust the deduction schedule at the employee level so that the deduction appeared in the special payroll run.
To simplify this workflow, we’ve made the following changes:
- Deductions will now appear in the payroll grid if they are effective on the pay date, even if not applicable as per the defined schedule.
- If the deduction does not apply to that paycheck according to the schedule:
- The system will not populate an amount.
- However, users can manually enter a one-time override amount for that paycheck.
This enables ad-hoc handling without modifying the deduction schedule.
New Work Location & Department Fields
Previously, the Work Location Name was not available on the payroll grid or in the import template, making it difficult for users to quickly identify, select, or deselect employees during payroll processing. This missing context often led to inefficiencies, especially for clients managing multiple work sites.
Payroll Grid Enhancements
- A new column "Work Location" has been added just before "Work Location State".
- By default, this column is deselected but can be easily enabled from column settings.
- This change improves visibility and makes employee filtering or selection by location much easier.
Payroll Import Template Enhancements
- Two new informational columns, "Work Location" and "Department", have been added before the "Job" column.
- These fields are optional and intended to help users better understand employee context during uploads.
- If you choose not to download the new import template and continue using an existing one, the existing template will remain supported.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article