March 12, 2026
Introduce new API features for failed payments and filing close dates to streamline billing processes.
Usage API: Payee Details on Failed Payment Records
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.
Filing Close Dates & Delayed Filing Billing
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.