Views:

1. Colorado OPT: employer tax support

Background: The Colorado Occupational Privilege Tax (OPT) includes an employer-paid portion; a flat per-head "head tax" applied for each employee working in certain Colorado localities. This employer portion was not calculating within employee payruns even when the jurisdiction was configured to calculate alongside employee payroll. The employee-paid portion of the tax continued to calculate correctly. This gap affected all Colorado OPT localities using this tax pattern, including Denver, Greenwood Village, Glendale, and Sheridan.

What's New?

The employer-portion Colorado OPT head tax now calculates correctly within employee payruns:

  • When an employer head tax is configured to calculate alongside employee payroll, it now appears on the employee's payrun results alongside the employee-portion tax.
  • The fix applies generally across all Colorado OPT localities using this head-tax pattern, not just Denver.
  • Off-cycle and non-employee payrun behavior is unchanged; the head tax continues to be excluded unless specifically configured to calculate with employee payroll.

2. Combined ACH: improved error handling

Background: When processing a large batch of ACH files using our new combined ACH process, any error encountered during a refresh or combine operation caused the entire process to halt immediately, with only a brief notification shown to the user. This meant an isolated or transient error in one file could block all other files from being processed and the error details disappeared before administrators could act on them. There was no persistent, per-file error visibility to help diagnose what failed and why.

What's New?

The updated ACH bulk operations now handle errors more resiliently and transparently:

  • ACH refresh: if an individual file fails, the error is logged and processing continues to the next file rather than halting the entire batch.
  • Combined ACH: since a combined file depends on all constituent files succeeding together, any error still halts the entire process immediately.
  • Errors are now displayed persistently in the ACH file grid with a badge and a plain-language message, rather than relying solely on a temporary notification.

 

3. Payroll enterprise wizard: remove $0 net checks

Background: The payroll enterprise wizard lacked a feature available in the classic payroll wizard that lets administrators identify and remove employees with $0 net checks before finalizing a pay run. Employees can generate a $0 check due to conditions like no hours entered or fully offset deductions. Without visibility into these checks in the payroll enterprise wizard, administrators either unknowingly processed unnecessary $0 checks or had to work around the limitation manually.

What's New?

Payroll enterprise wizard now brings $0 check visibility and removal to parity with classic:

  • During the pay run review and submit stage, a count and itemized list of employees with $0 check is now displayed.
  • A warning has been added to the Pay Run Assistant informing you of $0 checks in the pay run.
  • Administrators can select and remove one or more of these employees from the current pay run without affecting other employees.
  • Removed employees are excluded from the current pay run only and remain in the pay group for future runs.

 

4. Combined ACH: configurable start date for file retrieval

Background: The updated combined ACH feature surfaces up to two years of historical ACH files for clients to select from. For high-volume clients, this could mean many files loading simultaneously, causing significant performance degradation and making the "Select All" function unusable. No backend mechanism previously existed to limit the date range of ACH files returned.

What's New?

Backend support has been added for filtering ACH file retrieval by a configurable start date:

  • A new ACH start date setting can be configured per client to limit which historical ACH files are returned to the combined ACH screen.
  • If no start date is configured, a default 30-day lookback window is applied instead of returning the full two-year history.
  • The "Select All" function is now inherently scoped to the filtered result set, resolving the performance issues for high-volume clients.

Reach out to Support if you would like to specify the ACH start date for your workspace.

 

5. Settings: link added for general payroll settings

Background: A General Payroll Settings page has been released and is now included in Greenshades Online.

What's New?

A new link has been added under Settings > Payroll called General Settings, giving administrators direct in-product access to a new General Payroll Settings page.