Product updates

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.

We are introducing filing close dates to provide a clear boundary for when delayed filing billing applies.

Moving forward, Check will own responsibility for on-time filing if the company filing is unblocked at least 8 business days before the filing due date. After that day, Check will process all unblocked companies and close the filing. This will populate a closed_at date on the Tax Filing API and Console page.

Any company filing processed after the filing is closed will appear as a delayed_filing in the Usage API and on your invoice. This replaces the previous logic for delayed_filing or refile_attempt .

To avoid delayed filing charges, resolve company filing blockers prior to 8 business days before the filing due date.

Reminder: delayed_filing billing will not begin until April 1, 2026.

Usage records for payee_failed_payment now include a resource_information field that identifies the employee or contractor associated with the charge.

• resource_information.payee — the employee or contractor ID
• resource_information.payee_type — "employee" or "contractor"

This lets you attribute failed payment charges to specific workers without additional API calls, making it easier to generate clear, itemized bills for your customers.

For all other usage categories, resource_information returns {}. This is a non-breaking, additive change. See the Usage API docs for full details.