Payroll Tax Impounds: Who's Actually Holding Your Trust Fund Taxes

An ordinary payable that goes unpaid is a contract or collections problem between two parties. An unremitted trust fund tax is treated as a government fund the company held and failed to hand over, and the personal liability exposure for officers and controlling individuals reflects that distinction. This is why a payroll provider failing to remit on time is a serious event, not a minor service issue, and it's worth understanding exactly how your provider handles the impound before you need to rely on that understanding under pressure.

Most payroll providers debit your account for gross wages plus all withheld taxes around payday, hold the tax portion in a separate impound, and remit it to the relevant federal and state authorities on whatever deposit schedule your company is assigned, which can be next-day, semi-weekly, or monthly depending on your prior deposit history and size. Ask your provider directly which schedule applies to your company and confirm it matches what you'd expect given your payroll size, since being on the wrong schedule can itself trigger penalties even when the underlying tax is eventually paid.

Confirm whether your provider is registered as a reporting agent with the relevant tax authorities and whether they carry coverage for impounded funds specifically, not just general errors and omissions coverage. Ask what happens, procedurally, if a specific deposit fails to go through, whether you're notified immediately or only discover it at quarter-end reconciliation, since the gap between those two scenarios is where real damage happens.

A few patterns show up repeatedly:

• Switching payroll providers mid-quarter without confirming the outgoing provider remitted every deposit through the cutover date, leaving a gap nobody notices until a notice arrives months later.
• Assuming state withholding is covered the same way as federal, when a state's deposit schedule or registration requirement can differ meaningfully from the federal one.
• Treating provider confirmation emails as proof of remittance rather than periodically checking the tax authority's own online account for your business, which shows what was actually received.
• Not knowing your own deposit schedule, which means a mismatch between what your provider is doing and what's actually required can go undetected for a full quarter or more.

You don't need to run payroll tax deposits yourself to manage this risk well. You need to periodically confirm, directly with the tax authority rather than only through your provider, that deposits are landing on schedule, and you need to know who at your company is designated as the point of contact if a deposit issue ever surfaces. Building that check into a quarterly routine, rather than assuming it forever because nothing's gone wrong yet, is the actual control here.

Each state where you have employees may set its own separate withholding deposit schedule and registration requirement, independent of the federal one and independent of each other. Adding a new state through a single remote hire is a common way this gets missed, since nothing about hiring one person in a new state necessarily triggers a review of whether your provider is correctly registered and remitting there yet. Whenever you cross into a new state for the first time, confirm registration and deposit setup for that state specifically rather than assuming your provider handled it automatically.

The same applies when an employee moves states without formally changing roles, since payroll and HR sometimes learn about a relocation at different times, or not at all. A quiet gap between when someone actually starts working from a new state and when your payroll setup catches up is exactly the kind of gap that turns into a deposit registration problem months later.