Product updates

Previously, if a partner created their NEXT integration after their policy went live, payrolls were missed. NEXT now sends Check Support a “missed payroll” list and we automatically re-sync those runs. If an employer flags missing payrolls, open a Support ticket and we’ll handle the re-sync.

Washington employers now have the ability to configure Washington Labor and Industries (L&I) risk codes on a per-earning basis for their employees, which allows employees to perform work across multiple risk codes on a given payroll run. This is especially common in industries such as construction, where employees often perform many different types of work within a given pay period.

To enable this, partners need to be integrated with the Earning Code API. We have added the ability to provide a risk class code on the Earning Code, which if provided, will override the employee’s default risk class code and calculate WA L&I premiums at the provided risk class code’s rate.

This feature is not required for Washington L&I calculations and reporting. It only needs to be used if an employee wishes for their earnings on a given payroll to be split across more than one risk class code. By default, premiums will continue to be calculated using the risk code that is assigned to the employee in their company-defined attributes.

For more information about how Washington L&I is calculated, visit our Help Center documentation.

We have added support for two new benefit types, transit and parking, which can be used to define employee benefits for vehicle transportation and transit passes, and qualified parking benefits, respectively.

These benefits are excluded from taxable income under Section 132(f) of the Internal Revenue Code up to a monthly limit of $325 in 2025.

For the full list of benefit types supported in Check, refer to our API documentation.

Today we’re thrilled to release automated handling of Notifications of Change (NOCs). A NOC is a courtesy notice provided by banks, which means that a payment was processed successfully but some piece of account information needs to be corrected before the next payment to avoid future delays or returns.

Historically, Check has handled NOCs by disabling the bank account in question, but with this new release we will now automatically apply changes communicated via NOCs. Partners will be notified via webhook about these changes, and a new field on the Bank Account object — last_noc_correction_at — will be set to the time when we processed the NOC.

For more information, please visit our guide on Notifications of Change.