Product updates

Partners can now retrieve active funding failure strikes for a company via GET /companies/{company}/funding_strikes. Strikes represent funding failure offenses that factor into Check's processing period demotion and termination decisions.

Each strike includescreated_at , when the strike was issued.

For more details, see the API documentation.

We’re excited to announce new filing blocker management endpoints. You can now manage filing blockers via API, eliminating the dependency on Zendesk tickets for updating the majority of blocker types.

1. POST /filings/{id}/add_blockers with the blocker_type as an array in the body will place a blocker on a filing. In production, only held_by_customer is accepted. In sandbox, other issue types are accepted for testing.
2. POST /filings/{id}/remove_blockers with blocker_type as an array in the body will remove a blocker and return the filing to a pending status if all blockers are removed. Multiple types can be specified in a single request. Some blockers cannot be manually removed and the endpoint will return a descriptive error explaining why. Read more in our API Guide.

A few reminders to keep in mind:

1. We will automatically queue pending filings for refile if the filing is closed. Each refile attempt will count as a delayed_filing for billing, so ensure the underlying issue is resolved before removing the blockers.
2. The status_history value in the filing object is updated to include all of the blockers in the blocked_reason array. It previously only returned the most recently added blocked_reason.
3. This release replaces the API call to hold a filing that was previously announced. The add_blockers and remove_blockers APIs will take the place of the POST /filings/{id}/hold and POST /filings/{id}/release_hold that was previously proposed. The updated status_history functionality will replace the proposal for hold_history.

These changes are live today in Sandbox and Production.

Starting next week for Q1 2026 period end, a Tax Receipt will be generated for every balancing payroll. The receipt gives employers a clear breakdown of each tax adjustment resulting from period end balancing: what will be collected or refunded directly in an upcoming employer transaction vs. what will be refunded separately by the tax agency after filing.

The Tax Receipt is available once balancing payrolls are approved (April 2nd, for Q1 2026) and can be accessed as a PDF in Console — either from the balancing payroll on the Payroll Details page or the balancing transaction on the Transactions page. Read more about Balancing and the Tax Receipt in this Help Center article.

There are two new Communications objects you can subscribe to this quarter to have Check communicate upcoming balancing transactions, including the Tax Receipt, directly to your employers through white-labeled emails:

1. Filing Period Closed — Notifies employers of the scheduled collection or refund resulting from balancing, and includes the Tax Receipt as an attachment.
2. Tax Transfer Cancelled — Notifies employers that a previously scheduled transaction resulting from balancing has been cancelled (e.g., because the partner cancelled the transaction or a balancing payroll was reopened), and that the associated receipt is no longer current.

If you choose to use this feature to ensure that employers are notified in the event of changes to the original tax transfer, you need to subscribe to both Communications objects.

The Filing Period Closed Communication replaces the Upcoming Debit Variance Scheduled Communication for quarter end balancing transactions. Partners currently subscribed to Upcoming Debit Variance Scheduled have been automatically subscribed to both new objects. If you do not want to use these Communications this quarter, update your settings via the "Notifications" page in Console.