May 21, 2026

Enhance filing blocker details with notes and resource mappings, plus funding strikes and audit updates.

Enriched Filing Blocker Details

The blocked_reasons in the status_history of a Filing object now includes additional context to help you resolve issues without contacting support.

  1. There is a new field, note, so Check operators can provide additional context on blockers that we receive from agencies. This field is optional.
  1. We've added additional resource_type and resource mappings to some blocked_reasons. New resources include:
      • company_bad_standingresource_type: "payment", resource: "pyt_..." . The failed debit transaction is causing the company_bad_standing blocker.
      • missing_tax_fundsresource_type: "payroll", resource: "pay_..." . The payroll that is missing tax funds.
      • invalid_ssnresource_type: "employee", resource: "emp_..." . One employee on the filing with an invalid SSN. If there are multiple employees with invalid SSNs, the next one will populate after resolving the one shown.
      • invalid_tax_idresource_type: "company_tax_param", resource: "spa_..." . The setup parameter for this filing that has an invalid ID.
      • invalid_tax_rateresource_type: "company_tax_param", resource: "spa_..." . The setup parameter for the tax rate has an invalid rate entered.

      You can review the API documentation for these new items here.

Funding Strikes API

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.

Audit Details of Tax Parameter Changes in Console

We shipped a small improvement to the employee withholdings and company setup parameters views in Console. Now, every tax parameter setting card shows who last changed it, whether that was a Console user (by email), Check, or an API call.

This makes it much easier to answer "why does this employee have this withholding setting?" without digging through audit logs or reaching out to Support. This is a Console-only change.

Did this answer your question?
😞
😐
🤩