Overview

Two new data requirement messages (DRMs) now flag a missing school district code during payroll processing for resident and worksite addresses in Kentucky, Ohio, and Pennsylvania. These are warning messages only — they do not block payroll processing.

Why We Built It

Kentucky, Ohio, and Pennsylvania require a school district code for accurate local tax withholding. These two DRMs give Payroll Admins a heads-up during processing when that code is missing, so it can be corrected before the check is finalized.

What to Expect

For checks with a Kentucky, Ohio, or Pennsylvania address:

No configuration is required to use these DRMs, and no action is needed unless you choose to turn them off.

Overview

A new Classic AQ, OBBB Qualified Overtime Premium 2026, is now available under Reports. It pulls the OBBB-qualified overtime premium amount that Avionté already calculates automatically during payroll processing, so you can verify and report it for W-2 purposes without recalculating it by hand.

Why We Built It

Under the One Big Beautiful Bill (OBBB), qualified overtime premium pay is eligible for a federal income tax deduction for tax years 2025 through 2028, and employers must report the qualifying amount to employees on the W-2 (Box 14) or a separate statement. This new AQ gives users a purpose-built way to pull that amount straight from payroll, replacing the need to manually select overtime and regular pay codes to isolate the premium themselves.

What to Expect

The new AQ is available under Reports and includes:

No additional configuration is required. Full parameter and field details are available in the companion Knowledge Base article.

Overview

A new pay code group called LLH Pay Codes is now automatically created in Back Office for LLH Integrated clients. This group includes standard pay codes REG, OT, DT, and any custom pay codes containing the word “Salary,” enabling LLH to accurately identify which transactions apply to talent benefits calculations.

Why We Built It

LLH previously could not reliably determine which pay codes and transaction types to include in talent benefits calculations because clients customize their pay codes. While LLH applies to REG and Salary pay codes, only REG is standardized across clients. This configuration ensures LLH correctly identifies applicable transactions regardless of custom pay code naming conventions.

What to Expect

When LLH integration is active, the LLH Pay Codes group appears in Back Office payroll configuration and automatically contains REG, OT, DT, and any pay codes with “Salary” in the name. Clients can review and adjust this group if needed, but the default configuration covers standard pay code scenarios out of the box.

Overview

The State Saves Employee List AQ now outputs Email and Phone Number as two separate columns instead of one combined column for employees in Delaware, Maryland, Maine, Minnesota, New Jersey, New York, Nevada, Rhode Island, and Vermont.

Why We Built It

The official state reporting templates for these state savings (Secure Choice) programs require Email and Phone Number as two distinct columns. The previous combined column didn’t match those templates, which meant Back Office and Classic customers had to manually reformat the file before submitting it to the state, creating extra work and compliance risk.

What to Expect

When you generate the State Saves Employee List AQ for Delaware, Maryland, Maine, Minnesota, New Jersey, New York, Nevada, Rhode Island, or Vermont:

All other report fields, parameters, and behavior for these states are unchanged. No configuration is required.

Overview

A new branch access validation has been added to time entry batch verification in Back Office. When you verify a time entry batch, the system now checks whether your account has access to all branches represented in the batch's transactions. If any transaction belongs to a branch you cannot access, the system raises an alert identifying the specific branch and transaction, preventing unauthorized verification before it happens. For related DRM configuration, see the DRMs - Time Entry article.

Why We Built It

Back Office users operate with branch-level access controls for security and data integrity. Without a validation check at verification time, a user could unknowingly process payroll transactions for branches they are not authorized to access, creating compliance gaps and audit risks. This improvement enforces those access boundaries automatically at the point of verification.

What to Expect

If you verify time entry batches that include transactions across multiple branches, you may encounter this validation if any transaction belongs to a branch outside your access. The alert identifies the specific branch and transaction so you can resolve the issue, either by removing the restricted transaction from the batch or by requesting updated branch access from your administrator. If your access already covers all branches in your batches, no change in behavior is expected.

Administrators can set the severity to Severe (default — blocks verification) or Warning (alerts but allows verification to continue), or disable the rule entirely, in the Time Entry data rule configuration in Back Office. For more information, see the DRMs - Time Entry article.