Overview

Back Office and Classic payroll now calculate weighted overtime across extended bonus periods, such as quarterly bonus cycles. Select a date range when processing a bonus, and the system spreads the bonus evenly across each workweek, works out the hourly equivalent, and calculates any overtime owed — no manual spreadsheet work required.

Why We Built It

Calculating weighted overtime for quarterly bonuses previously required manual work outside the system, followed by re-entering the results into time records — a slow process that left room for error. This feature automates the calculation in accordance with 29 C.F.R. § 778.209(a-b), reducing manual effort and helping ensure accurate overtime payments at bonus payout time.

What to Expect

When processing a quarterly bonus, select a date range using the new option in the card view or Actions menu. The system then:

The calculated weighted overtime amount is included automatically in the bonus payout. No manual calculation or re-entry is required.

Overview

A new Data Requirement Message (DRM), ppv_CheckForMultipleWorksitesWithTaxes, triggers when there is more than one worksite on a check, and/or when there are taxes for more than one location (State, City, Local). The DRM raises a Warning finding, once per payee regardless of how many transactions are on the check.

Why We Built It

Employees who work at multiple locations may be subject to different tax obligations at each worksite. Without this check, payroll could process with a zero tax amount on one worksite's transactions, causing inaccurate withholding and potential compliance issues. This DRM surfaces the mismatch so payroll users can review it before the check is finalized.

What to Expect

Once enabled for a branch, a payroll batch with an employee spanning two or more worksites with differing State, County, or City tax geocodes will show a Warning finding during payroll process verification. Review the employee's worksite tax setup and correct any mismatched configuration as needed; the Warning does not block posting the batch.

Overview

Avionté now integrates with retirement savings plan administrators, giving staffing firms the ability to manage 401(k) and Simple IRA enrollment, payroll deductions, and contribution updates directly through the platform. The integration connects through a third-party administrator (TPA), so clients can work with a wide range of retirement plan providers through a single integration.

Why We Built It

Retirement savings mandates are expanding fast. More than 20 states currently require staffing firms to offer a retirement savings option, and legislation is active or pending in most others. Managing enrollment, deductions, and remittance across disconnected systems creates real administrative burden and compliance risk. This integration keeps payroll deduction amounts synchronized with the retirement plan portal automatically, so coordinators spend less time reconciling data between systems and more time on placements.

What to Expect

The integration supports the full retirement savings workflow:

No additional configuration is required. Additional details and setup guidance are available in the Knowledge Base.

Overview

The City of Bloomington, MN repealed its local Earned Sick and Safe Time (ESST) ordinance effective April 27, 2026. The Bloomington-specific ESST accrual plan has been removed from Avionté Back Office and is no longer available for selection. Clients with workers in Bloomington are now governed solely by the Minnesota statewide ESST law (Minn. Stat. §§ 181.9445-181.9448).

Why We Built It

When a local ordinance is repealed, payroll systems must be updated to reflect current legal requirements. Leaving an invalid accrual plan available as a selectable option creates compliance risk. Removing the Bloomington plan ensures clients cannot inadvertently configure employees under a no-longer-valid local ordinance.

What to Expect

The Bloomington, MN ESST accrual plan no longer appears as a selectable option in Back Office. Clients who previously used this plan will have their employees' Bloomington accrual records marked inactive with an end date of April 27, 2026. Employee accrual balances and historical data are fully preserved -- no accrual data is lost during this transition. Going forward, employees in Bloomington should be configured under the Minnesota statewide ESST plan. If you need assistance transitioning employees from the Bloomington ESST plan to the Minnesota statewide plan, contact Avionté Support.