March 2026

What is the improvement?

The Payment Register report now includes a Funding Type parameter and output column. Use the new parameter to filter results by ACH, Non-ACH payments, or Both, and view the funding type for each payment directly in the report output.

Why?

Separating ACH and Non-ACH payments previously required building a custom report. The Funding Type filter lets you segment payment data directly within the standard Payment Register — no custom report needed.

How does this impact you?

The Funding Type parameter appears in the report filters alongside existing options like Date Type and Branch. Select ACH, Non-ACH, or Both to view all payments. A Funding Type column now appears in the report output, displaying the funding method for each payment record.

For full parameter and field details, see the Standard Report - Payment Register KB article.

System Setting/User Permission Update: None

What is the improvement?

When performing an invoice correction, you can now fully remove a PO number rather than being required to replace it with a new one.

Why?

Requiring a replacement PO number during invoice corrections created confusion and added unnecessary administrative steps to the process. This update removes that requirement, streamlining invoice management for cases where a PO number is no longer needed.

How does this impact you?

If an invoice no longer requires a PO number after a correction, you can remove it without entering a replacement. No configuration changes or permission updates are required.

System Setting/User Permission Update: None

What is the improvement?

A new CPP2 EE column will be added to the Payroll Journal_CA report, positioned after the existing CPP column.

Why?

Previously, CPP and CPP2 contributions could not be viewed separately in the Payroll Journal_CA report, which could create confusion when reviewing and reconciling Canadian payroll. This update gives CA clients a clearer view of each contribution type directly within the report.

How does this impact you?

CA clients will now see CPP2 EE as a distinct column in the Payroll Journal_CA report. No action is needed on your end.

System Setting/User Permission Update: None

What is the improvement?

The IRS has increased the 1099-NEC reporting threshold from $600 to $2,000, effective for payments made on or after January 1, 2026. Avionté is updating its 1099-NEC reporting, and data sent to Greenshades where applicable, to reflect this new limit. Beginning January 1, 2027, this threshold will be adjusted annually for inflation, meaning the required reporting amount may change each year going forward.

Why?

With the passing of the OBBB, the 1099-NEC reporting threshold was increased from $600 to $2,000.

How does this impact you?

AviontéBOLD will automatically apply the updated $2,000 threshold when generating 1099-NEC reports for the 2026 tax year. If your agency uses Greenshades for tax filing, the updated threshold will also be reflected in data sent to Greenshades. No action is required on your part to activate this change.

Starting with the 2027 reporting year, the threshold may be adjusted for inflation. Watch for updates in future release notes confirming any annual threshold changes.

For instructions on running the 1099-NEC report, see: 1099-NEC Report

System Setting/User Permission Update: None

What is the improvement?

The Form 941 report has been updated to reflect the 2026 IRS revision, including a new Aggregate Return Filers section, a language update in Part 1, and removal of the payment voucher, as well as several other small changes to ensure compliance.

Why?

The IRS releases an updated Form 941 each year, and the report must match the current revision to ensure accurate filing. These updates keep the report aligned with 2026 form requirements so your quarterly filings reflect the correct instructions and structure.

How does this impact you?

Several fields and sections have been updated to ensure the report matches the 2026 Form 941 released by the IRS for compliance. No action is required on your end.

System Setting/User Permission Update: None

What is the improvement?

Workers Comp issues previously caused by the supplier end date have been resolved in two ways. The existing DRM has been updated to look at the week worked instead of the accounting period in time entry. Additionally, a new payroll DRM has been added that runs through the same validation using the check date.

Why?

The DRM in time entry was previously based on the accounting period, which could lead to errors in Workers Comp rate calculations. The updated and new DRMs ensure this validation is applied at the correct points in the process, preventing those errors from occurring.

How does this impact you?

No changes, permission updates, or settings adjustments are required on your end.

System Setting/User Permission Update: None

What is the improvement?

The filing status "Percent Based on Annual Gross" has been removed from the filing status options for AZ-based talent.

Why?

Arizona has updated their filing statuses and no longer includes "Percent Based on Annual Gross" as a valid option. This change ensures AZ withholding remains compliant with the state's current requirements.

How does this impact you?

This update is automatic and no action is required. Any talent currently assigned this filing status will be automatically updated to AZ No State 2023 A4 Filed.

System Setting/User Permission Update: None

What is the improvement?

AviontéBOLD now displays a warning in time entry when a talent does not have enough accrued hours to cover a PTO transaction on a custom accrual plan. This extends existing balance-check functionality — previously available only for sick leave plans — to all custom PTO accrual plans.

Why?

Entering PTO time against an insufficient balance can create payroll discrepancies and require time-consuming corrections after the fact. By surfacing this warning at the point of time entry, Back Office users can catch and address balance issues before they move further through the payroll process, reducing downstream errors and saving time on corrections.

How does this impact you?

When entering time for a talent on a custom accrual plan, AviontéBOLD will automatically check whether the transaction will bring the talent's accrued balance negative. If it will, a DRM warning appears alerting you that the talent does not have enough accrued time. This is a warning, not a hard stop, so you can still proceed if needed.

No configuration changes are required if your custom accrual plans are already set up with a deplete transaction type. If a custom plan does not have a deplete transaction type assigned, the warning will not fire. Confirm your plan setup in accrual plan settings if you are not seeing the warning as expected.

System Setting/User Permission Update: None

What is the improvement?

The ADP Employment Tax integration now supports a new parameter that allows you to generate quarterly tax files by FEIN rather than by individual Supplier. When multiple Suppliers share the same Federal Employer Identification Number, you can consolidate them into a single quarterly file with one setting.

Why?

Customers using the ADP Employment Tax integration who have multiple Suppliers sharing the same FEIN previously had to generate separate quarterly files for each. This parameter allows those Suppliers to be consolidated into a single file, reducing manual effort during quarterly tax filing.

How does this impact you?

When generating your quarterly ADP Employment Tax file, a new parameter is available: Include all Suppliers with same FEIN. Use the table below to understand your options:

System Setting/User Permission Update: None — the parameter is available directly within the quarterly file generation workflow.

What is the improvement?

An amendment to the NYC Earned Sick and Safe Time Act (ESSTA) has added a new sick leave type for New York City.

Why?

New York City recently passed an amendment to the ESSTA that requires employees receive 32 hours of unpaid sick leave when they begin a new position. This sick leave renews each calendar year.

How does this impact you?

If you employ staff in NYC, this accrual plan has been automatically inserted into your system to help you comply with the new law, effective February 22, 2026.

System Setting/User Permission Update: None

What is the improvement?

AviontéBOLD now includes the 1099-NEC AQ report, a standard year-end report that surfaces 1099-NEC data for all applicable nonemployee recipients. Staffing agencies can export, review, and audit nonemployee compensation totals by recipient, view box-level detail, and export records to Excel for reconciliation — all from a single report.

Why?

Year-end 1099 filing is one of the most time-sensitive compliance tasks staffing agencies manage. Previously, gathering this data required pulling from multiple sources or relying on manual processes, increasing the risk of errors and delays during an already compressed filing window. The 1099-NEC AQ centralizes recipient data, box-level figures, and tax identification details in one place, making it faster to verify accuracy and export records for reconciliation before deadlines hit.

How does this impact you?

Access the 1099-NEC AQ report through the standard reporting area in AviontéBOLD. Select your supplier, branch, and tax year, then choose a return type — Detail, EE Summary, ER Summary, or W2 Count — based on what you need to review. Export results to Excel for counts and reconciliation. For full parameter and field descriptions, see the 1099-NEC AQ Knowledge Base article.

System Setting/User Permission Update: None