April 9, 2026
Manage your Q1 payroll transactions and enhance filing blocker resolutions effectively today.
Quarter End Date Reminders
All Q1 balancing payrolls were approved last Thursday, April 2nd. Any balancing payrolls that resulted in a direct transaction to the employer (either a collection or refund) will begin processing tomorrow. The last chance to cancel these transactions is tonight, April 9th at 11:59 PM ET.
Employer copies for Q1 filings will begin publishing on Friday, April 10th. These copies will include a draft watermark until they are filed with the agency.
While quarter end balancing was completed last week, in select cases, we may receive feedback from tax agencies at the time of filing regarding incorrect rates set by employers during the period. This feedback can result in corrections to ensure the employer's tax liabilities are correctly adjusted and are performed immediately to unblock filing.
Enhanced Filing Blocker Management
This quarter, we’re focused on helping you resolve filing blockers faster and with less back-and-forth, while automating much of the delayed filing process. So far, we’ve introduced closed_at to provide a clear boundary for when delayed filing billing applies, begun processing those filings in regular sweeps, and removed the need to submit a Zendesk ticket for blockers that can be resolved automatically (e.g. applied-for IDs).
What’s Releasing Now
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.
POST /filings/{id}/add_blockerswith theblocker_typeas an array in the body will place a blocker on a filing. In production, onlyheld_by_customeris accepted. In sandbox, other issue types are accepted for testing.
POST /filings/{id}/remove_blockerswithblocker_typeas an array in the body will remove a blocker and return the filing to apendingstatus 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.
What’s Coming Soon
We plan to enrich each entry in blocked_reasons with a human-readable description that tells you exactly what to fix — including specific employee names, dollar amounts, and tax IDs — along with an optional operator note for additional context. We'll also be bringing blocker management into Console, so you can see what's blocking a filing, resolve it, and request a refile all in one place.