We saw this play out on a US client's account this year. In November, the IRS sent a Notice CP136 confirming the client's federal tax deposit schedule for the coming year had changed, from monthly to semi-weekly, based on the total tax reported over the prior four quarters. The notice went to the business's registered address. Nobody forwarded it to the person running payroll. Payroll kept depositing on the old monthly schedule into January, and the first deposit under the new semi-weekly requirement was late the moment it should have gone out. A follow-up notice arrived a few months later with a failure-to-deposit penalty and interest attached, for a deposit that would have been on time if the CP136 had reached the right inbox two months earlier.
Nothing about the payroll platform itself was broken. It deposited exactly what it was told to, on the schedule it had on file. That is the pattern worth naming directly: a payroll provider is a remitter, not a registrar. It pays the tax agencies you are already registered with, on the schedule it has been given. It does not independently know your federal deposit frequency changed unless someone tells it, and it does not register your business with a new state tax agency the moment you hire someone there. Both of those stay the employer's job, and the gap between "we use a full-service payroll provider" and "every payroll tax obligation is covered" lives exactly in that difference.
A payroll provider is a remitter, not a registrar — the gap between those two words is where the notice comes from.
What CP136 Actually Says, and Why It Gets Missed
CP136 is not a bill. It is the IRS's annual notice to any employer filing Form 941, telling you whether your deposit schedule for the coming calendar year is monthly or semi-weekly. The determination is mechanical: the IRS totals the tax reported across four quarters, the lookback period, ending the prior June 30. Report more than $50,000 in that window and the new year's schedule becomes semi-weekly. Report less, and monthly usually applies. The notice typically goes out in November for the year starting the following January.
Where this breaks down operationally: the CP136 is addressed to the employer, at the employer's address on file, not to the payroll provider or the accounting firm managing the books. If the business owner, an office manager, or whoever opens the mail doesn't recognize what it is or doesn't know to forward it, the new schedule never reaches whoever is actually running payroll. Deposits continue on the old frequency by default, because nothing about the payroll system changes on its own.
What a Late Deposit Actually Costs
The failure-to-deposit penalty under IRC 6656 is four-tiered, and it applies regardless of whether the return itself was filed correctly and on time:
- 2% for deposits 1 to 5 days late
- 5% for deposits 6 to 15 days late
- 10% for deposits more than 15 days late, or for any deposit not made electronically through EFTPS
- 15% if the amount is still unpaid more than 10 days after the IRS sends a notice demanding it
Interest accrues separately on top of whichever tier applies. None of this requires the IRS to prove anything beyond the deposit date against the required schedule; it is calculated mechanically off the calendar.
The one piece of relief worth knowing
The IRS can remove the failure-to-deposit penalty specifically for the first required deposit after a deposit frequency change, provided the related employment tax return is still filed by its due date. It is narrow, it covers exactly one deposit, and it does nothing for every deposit after that one made on the wrong schedule. In our client's case, this covered the first missed deposit; it did not cover the second one, made three weeks later before the schedule correction was caught.
The State-Level Version of the Same Gap
The federal deposit-schedule case is one shape of this problem. The more common shape shows up at the state level, and it is triggered by something that rarely gets routed through accounting at all: a single new hire in a state the business has never had an employee in before, often a remote hire approved in a hiring conversation with no payroll implication flagged.
State tax agencies require an employer to hold a registered withholding account number before any tax can be remitted there. Registration commonly takes several weeks. A payroll provider cannot remit to an agency it has no account number for, and its standard position is that this registration is the employer's responsibility, not something the platform does on your behalf. The clock on registration should start the day the hire is approved. In practice, it starts whenever accounting finds out, which is often the first payroll cycle that hire is due to be paid in, weeks after it should have started.
The mismatch that causes the notice: registration takes weeks. The payroll deposit deadline does not move to accommodate it. Whatever falls in that gap, an unregistered agency with tax due and nowhere to remit it, becomes a notice, a penalty, and interest, and none of it lands on the payroll provider, because the provider was never the party responsible for registering the account in the first place.
Putting This on the Right Checklist
Route new hires in a new state through accounting before the first payroll run, not after
A new hire in a state you don't already operate in should trigger a state registration check the same day the hire is approved, not the week payroll is due to run. This belongs on the hiring checklist, not the payroll checklist, because by the time it reaches payroll the registration clock has already lost however many days sat between approval and the first pay date.
Name someone responsible for forwarding IRS and state deposit-schedule notices
A CP136, or its state equivalent, needs a defined destination the day it arrives, not "whoever opens the mail that week." If your payroll is outsourced or run through a platform, confirm explicitly who updates the deposit schedule on that platform when the notice changes it, and don't assume the platform will catch it from your filing history alone.
Reconcile the deposit schedule annually, not just when a notice arrives
The lookback period recalculates every year based on the prior four quarters. A business that grew past the $50,000 threshold this year may not remember to check whether that changed its schedule for next year, especially if the notice gets missed once already.
Frequently Asked Questions
Where to Go From Here
For the broader multi-state exposure this kind of gap sits inside, see our guide to US sales and use tax nexus, which covers the same registration-before-deadline mismatch on the sales tax side. If payroll and compliance keep landing on whoever happens to be free that week, our outsourced finance team page covers what it looks like to have this owned properly instead.
We catch the notice before it becomes a penalty, not after.
Multi-state payroll compliance fails less often because of a bad payroll platform and more often because nobody was assigned to catch the notice, forward the schedule change, or start the registration clock on day one. That ownership is what we build into an engagement, not a feature you have to remember to ask your payroll provider for.
Talk to an Expert → Book a Call Today →