Product updates

We’re excited to announce our redesigned and enhanced NEXT workers’ compensation component.

This is a no-op upgrade to the existing NEXT integration component, and there’s nothing to build from your side. We’ve made cosmetic improvements to the overall flow, reworked the UX, and added broker of record switcher functionality to lift funnel conversion. A quick look at what your employers will see:

1. Three options upfront: a new workers’ comp plan, connect an existing NEXT policy, or transfer Broker of Record (BOR)

2. In-component BOR transfers: businesses with workers’ compensation elsewhere can start the Broker of Record switch right here; the old blank “with an agent” screen now shows real status.

3. A real “your coverage” view: active policies show carrier, premium, billing, and coverage period (fetched from the NEXT API), instead of a bare “Manage plan” link-out.

We plan to release this component to GA in two weeks, on July 2.

You can now view and resolve most company filing blockers directly in the company tax filings details page in Console, without creating Zendesk tickets.

You should work with employers to resolve issues with the agency and then directly remove the resolved blocker(s) from the filing. This will automatically queue Check to file it, expediting the process of filing originals and refiles.

Some blockers will have more context explaining what happened and how to resolve it. We are adding optional notes from the agency on blockers, as well as additional resources linking blockers to their root cause. This information will assist your employers in understanding the blockers and taking the correct resolution path. You can also find this information available in the API.

Note that each blocker has a different resolution method. They can be resolved by providing the information, confirming action was taken with the agency, or, in a few cases, requesting a Zendesk ticket. More information about how to manage each blocker can be found in our Help Center article Requesting refiles in Console.

On June 15th, Tax Filings API, Console, and Blocked Filings Report will begin including new blocker reasons. These reasons provide clearer explanation of filing issues.

We’ve expanded tpa_failure to include four additional blocker types: tpa_failure, tpa_inactive, tpa_incorrect_access, tpa_linked_to_other_provider

Plus, we’ve added four new blocker types:fein_and_tax_id_mismatch,  incorrect_risk_class_code, incorrect_experience_factor, and customer_filing_required.

Lastly, we are renaming already_filed to filed_by_customer.

You can review the associated resources and how to resolve these issues in our API documentation.

We’ve created a Filings API Integration Guide to provide a visual example of how to best integrate with the Filings API and detail how to configure the backend. Actions like surfacing filing blockers early and providing a pathway for employers to remove blockers directly in product should increase your filing success rate.