Enrolled Agent Representation Lab
All Episodes

Stopping a 941 Penalty Cascade

Learn how to dissect an IRS payroll tax penalty notice, verify the underlying facts with transcripts and EFTPS traces, and use IRC Section 6656(e) to stop a penalty cascade before it spreads. The episode also contrasts First Time Abate with Reasonable Cause and closes with a practical five-step response checklist for handling Form 941 deposit issues.


Chapter 1

The Six Thousand Two Hundred Dollar Cascade Deconstructing IRS Notice CP161 and Form 941 FTD Penalties

Elena Carter

Imagine a client walks into your office, drops a letter on your desk, and... well, they are in a complete panic. It is November 24, 2025. The client is Apex Logistics LLC, and the IRS just sent them a Notice CP161 asserting a six thousand two hundred dollar Failure to Deposit penalty. That is under IRC Section 6656, assessed on their third quarter 2025 Form 941 where total payroll tax liability was sixty two thousand dollars.

Elena Carter

Now, as a practitioner, before you pick up the phone or draft a response, you have to separate what is confirmed, what is merely an assertion, and what is still completely unconfirmed. What do we actually know as fact here? We know the notice date, November 24, 2025. We know the return was processed, and we know the full sixty two thousand dollar tax liability has been paid. But the client asserts that the late deposit on September 15 was caused by a three day electronic clearinghouse failure at their bank. That is a taxpayer assertion, not a proven fact. And everything else, like whether the IRS applied the deposit to an earlier quarter or how the system calculated the math, remains unconfirmed until you pull the transcripts.

Elena Carter

Step one is absolutely non negotiable. You must secure the Form 941 Account Transcript and the EFTPS payment trace receipts immediately. Do not rely on client bank statements alone. You have a strict thirty day window from the CP161 notice date to respond before the automated system escalates to CP501 and CP503 collection notices. And remember your governing authority here. Section 6656 and Treasury Regulation 301.6656 1 are binding statutory and regulatory authority. The Internal Revenue Manual, specifically IRM 20.1.4, gives you insight into IRS processing procedures, but it is non binding guidance. You cannot cite the IRM as substantive law in a court, though it is invaluable for administrative navigation.

Elena Carter

Let us look at how that penalty hit six thousand two hundred dollars. IRC Section 6656 sets up a tiered penalty structure based on how late the deposit is. If you are one to five days late, the penalty is two percent. Six to fifteen days late, it jumps to five percent. More than fifteen days late, it climbs to ten percent. And if you fail to pay within ten days of a notice, it caps at fifteen percent. So on a sixty two thousand dollar liability, a ten percent penalty hits exactly six thousand two hundred dollars.

Elena Carter

But here is where practitioners often save the day, and it comes down to a critical, often overlooked provision: IRC Section 6656(e). Under standard IRS accounting, deposits are applied on a FIFO basis, first in, first out. That means if one deposit is late, every subsequent deposit in that quarter gets sucked into fixing the prior shortfall, creating a cascading sequence of late penalties across the entire quarter! Section 6656(e) gives the taxpayer the statutory right to designate how a deposit is applied, provided you submit that designation within ninety days of the CP161 notice. By designating the payments to specific deposit liabilities, you cut off the cascade immediately and isolate the penalty to the single late payment.

Chapter 2

First Time Abate vs Reasonable Cause Framing the Abatement Strategy

Elena Carter

Once you stop the cascade, you have to choose your abatement pathway. And you essentially have two routes: administrative First Time Abate, or statutory Reasonable Cause. First Time Abate, found in IRM 20.1.1.3.3.2.1, is an administrative waiver. If the taxpayer has a clean compliance history for the preceding three years, meaning no penalties assessed on Form 941 for twelve consecutive quarters, the IRS will administrative remove the penalty regardless of why it happened.

Elena Carter

In my practice and teaching, I see so many practitioners jump straight into arguing reasonable cause the moment a client mentions a bank error. They assemble giant packages explaining the bank glitch, spending hours of billable time. But a technical glitch does not automatically satisfy ordinary business care under Section 6656(a). The IRS high standards require showing that the taxpayer exercised ordinary business care and prudence, but was still unable to make the deposit on time due to circumstances beyond their control.

Elena Carter

That is where your intake interrogation and Circular 230 diligence come in. You must ask the right questions up front. Did the business have sufficient funds in the account on the deposit date? Was the failure caused by the bank or by the taxpayer payroll manager missing a deadline? What do the service level agreements with their payroll provider say? Under Circular 230 Section 10.22, you are required to exercise due diligence as to accuracy. And under Section 10.51, submitting an unverified or fabricated claim that a bank system crashed when it was actually a late wire submission is a severe ethical violation.

Elena Carter

So what is our action plan? First, check the account transcripts for the prior three years. If those twelve quarters are clean, pick up the phone and request an immediate First Time Abate over the phone. It is fast, clean, and definitive. However, while you are requesting FTA, you should simultaneously collect the bank wire system logs and affidavits to build a Form 843 Reasonable Cause package as a secondary position.

Elena Carter

Here is the golden principle of taxpayer representation in these cases: Never litigate Reasonable Cause when administrative First Time Abate offers clean, complete relief, but always preserve your Reasonable Cause proof in case prior year transcript audits uncover an unexpected minor penalty that invalidates FTA eligibility.

Elena Carter

To wrap this up, keep this compact five step checklist in your toolkit whenever a 941 penalty notice hits your desk. Step one, secure Form 2848 Power of Attorney. Step two, pull three years of 941 account transcripts to check FTA eligibility. Step three, obtain EFTPS trace logs to verify exact payment timing. Step four, evaluate an IRC Section 6656(e) designation to stop any penalty cascade. And step five, execute via phone FTA or file Form 843 with full supporting documentation. Master those five steps, and you will turn a six thousand dollar disaster into a routine administrative win.