Product updates

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.

We've expanded CheckAI with 29 new actions across 6 resource types, giving partners more self-service capabilities directly through the AI assistant.

What's New

• Pay Schedules — List, view, create, update, and delete pay schedules, plus retrieve upcoming paydays for a schedule.
• Employee Benefits — Full management of employee-level benefit enrollments: list, view, create, update, and delete.
• Company Benefits — Configure and manage company-level benefit plans with list, view, create, update, and delete support.
• Post-Tax Deductions — Set up and manage post-tax deductions (including miscellaneous and child support types) with list, view, create, update, and delete actions.
• Earning Rates — List, view, create, and update earning rates for employees.
• Earning Codes — List, view, create, and update company earning codes.

For more details on what CheckAI can do, visit our Help Center for details.

We are introducing a new submitted status to the Filing API that provides visibility into filings that have been sent to the agency but are not yet accepted. This will be available in Sandbox on March 16th and will merge to production on March 30th.

What is changing:

• The Filing API now supports five statuses: inapplicable, pending, blocked, submitted, and filed
• The new submitted status indicates a filing has been sent to the tax agency and is awaiting processing. The definitions of the other statuses are unchanged.
• The filing date (when a filing was submitted to the agency) is available via the status_history array. Use the most recent entry where status = "submitted" and read its status_at value. We recommend labeling this as "Filing Date" in your UI.
• filed_at continues to represent when the agency accepted the filing

What you need to do:

• If you filter by status: Add submitted to your recognized statuses
• If you display filing status: Add a display treatment for submitted
• If you display a filing date: Use status_history to extract the submitted date (see API documentation below)