Reasonable Cause Penalty Abatement: What Actually Counts

What is reasonable cause penalty abatement?

Reasonable cause is the relief route the IRS uses when a taxpayer exercised ordinary business care and prudence yet still could not file, pay, or deposit on time. It is judged case by case on all the facts, and the reasons that qualify depend on which penalty is at issue.

The IRS opens its guidance on penalty relief for reasonable cause with a sentence that does most of the work: reasonable cause is determined on a case by case basis considering all the facts and circumstances of the situation. There is no form to check a box on, no qualifying event schedule, and no threshold that guarantees a result.

That case by case framing is why two people with the same illness on the same dates can receive different answers. The question is never only what happened. It is whether what happened explains the specific lateness the specific penalty was charged for, and whether the taxpayer behaved reasonably before, during, and after the event.

One structural point matters before anything else. Reasonable cause is not available for every penalty, and where it is available, the reasons that count are shaped by the specific code section behind that penalty. The IRS says this directly: the reasons that qualify depend on the type of penalty owed and the laws in the Internal Revenue Code for each penalty. A story that satisfies the failure to file penalty is not automatically the right story for an accuracy penalty.

For businesses there is an additional wrinkle worth noting. The IRS applies the reasons to the person who had authority to submit the return, deposit, or tax. The relevant conduct is that person's conduct, not the entity's in the abstract.

What test does the IRS actually apply?

The standard is ordinary business care and prudence, meaning the degree of care a reasonably prudent person would exercise. The Penalty Handbook directs reviewers to weigh the stated reason against the dates of the penalty, the prior compliance record, the length of the delay, and whether the event was foreseeable.

The operative language lives in the Penalty Handbook at IRM 20.1.1. Ordinary business care and prudence includes making provisions for business obligations to be met when reasonably foreseeable events occur. A taxpayer establishes reasonable cause by showing facts that demonstrate that degree of care, taking the care a reasonably prudent person would exercise, and still being unable to comply.

The manual then tells reviewers exactly what to consider. Five questions run through the analysis, and they are worth reading closely, because a request that answers only the first one is a request that answers one fifth of what is being asked.

1. 1.What happened, and when did it happen?
2. 2.During the period of noncompliance, what facts and circumstances prevented the return from being filed, the tax from being paid, or the law from otherwise being complied with?
3. 3.How did those facts and circumstances actually result in the noncompliance?
4. 4.How were the remainder of the taxpayer's affairs handled during that same time?
5. 5.Once the facts and circumstances changed, what attempt was made to comply?

Question four is the one most requests never address, and it is quietly decisive. A reviewer comparing a claim of total incapacity against a period in which every other obligation was met on time is looking at a contradiction. The manual also instructs reviewers to check at least the three preceding tax years for payment patterns and overall compliance history, and it notes that the same penalty previously assessed or abated may indicate the taxpayer is not exercising ordinary business care.

There is also a first time argument that does not work the way people expect. The manual says that if this is the taxpayer's first incident of noncompliant behavior, that factor is weighed alongside the other reasons given, because a first time failure to comply does not by itself establish reasonable cause. A clean record is the engine of the separate administrative waiver, covered at first time penalty abatement, rather than a reasonable cause argument in its own right.

Two more sources sit behind the standard. Policy Statement 3-2, on reasonable cause for late filing or failure to deposit or pay, appears in the servicewide policy statements, and the accuracy related penalty draws on Treasury Regulation 1.6664-4. The IRS cites both on its own reasonable cause page, which is a useful signal about where the real criteria live.

Which circumstances count as reasonable cause?

The IRS lists fires and natural disasters, an inability to obtain records, and death, serious illness, or unavoidable absence of the taxpayer or an immediate family member. System issues that delayed an electronic filing or payment also appear. None of them is automatic, because each still has to explain the specific delay.

The published examples of valid reasons for failing to file or pay on time are short. What the Penalty Handbook adds is the evidence each category actually gets tested against, and that is where a request either holds up or does not. The table below pairs each recognized circumstance with the information the manual tells reviewers to look for.

Two of these carry limits worth naming. For death, serious illness, or unavoidable absence in a business setting, the manual asks whether the affected person had sole authority to execute the return, make the deposit, or pay the tax. If someone else was authorized, the reviewer considers why that person did not meet the obligation, and whether relying on a single authorized person was itself consistent with ordinary business care.

For disasters, the manual is blunt that one of these circumstances by itself does not necessarily provide penalty relief. A separate and much simpler route often applies first: taxpayers in a federally declared disaster area frequently receive postponed deadlines systemically, without any request at all, which makes a reasonable cause argument unnecessary for that period.

Which reasons does the IRS usually reject?

Four recur in the guidance: reliance on someone else to file or pay, lack of knowledge of the law, a mistake or oversight, and lack of funds standing alone. Each is treated as falling short of ordinary business care, though the guidance leaves a narrow opening where surrounding facts support the request.

The IRS publishes these four as factors that do not generally qualify. Read carelessly, they look like flat prohibitions. Read against the Penalty Handbook, each one is a presumption with a stated exception, and the exception is usually where a real request lives.

Forgetfulness sits in the same family and gets the shortest treatment of all. The manual says relying on another person to perform a required act is generally not sufficient, and that the responsibility to file a timely return and make timely deposits or payments cannot be delegated. That sentence recurs across several subsections, which is a fair indication of how often the argument is made.

The ignorance of the law subsection is the most forgiving of the four, and it is worth quoting the shape of it. Reasonable cause may be established where a good faith effort was made to comply, or where the taxpayer was unaware of a requirement and could not reasonably be expected to know of it. In the same breath the manual warns that reasonable cause should never be presumed, even where ignorance is claimed.

Does relying on a tax professional count as reasonable cause?

It depends on what the professional was relied on for. Relying on an advisor for advice on a genuinely technical question can support relief, mostly for the accuracy related penalty. Relying on someone to file or pay generally does not, because the Penalty Handbook treats that duty as one that cannot be delegated.

This is the single most confused point in the topic, and the confusion is understandable, because both halves of the answer are true at once. Summaries that say professional reliance never works are wrong, and summaries that list it as a standard qualifying reason are also wrong. The manual splits the question in two before answering it.

The Penalty Handbook opens its erroneous advice subsection by asking reviewers to identify which claim is being made. Is the taxpayer saying they did not comply because of specific advice received from someone, orally or in writing? Or is the taxpayer saying they relied on someone else to comply on their behalf? Those two claims travel down different paths.

The manual illustrates the working version with an employer classification example. An employer researched the available IRS publications on contract labor, gave the advisor clear documentation of what the workers actually did, and asked for an opinion on whether they were contract labor or employees. The advisor said contract labor. The IRS later determined they were employees. That fact pattern is the shape of a reliance argument that has somewhere to go.

Notice what carries the weight in that example. The taxpayer did the research, produced complete documentation, and asked a specific question on a genuinely hard issue. The manual then draws the boundary explicitly: relief based on reliance on the advice of a tax advisor is limited to issues generally considered technical or complicated, and the responsibility to file, pay, or deposit generally cannot be excused by that reliance.

For the accuracy related penalty the accuracy related penalty framework asks a parallel set of questions: the efforts made to report the correct tax, the complexity of the issue, the taxpayer's education, experience, or knowledge of tax law, and the steps taken to understand the obligation or seek help. Where an advisor was used, the IRS also considers whether all needed information was provided and whether the advisor was competent and experienced with the situation.

Which penalties can reasonable cause reach?

Failure to file, failure to pay, and failure to deposit are the common candidates, and the accuracy related penalty is judged under its own good faith standard. The IRS states plainly that reasonable cause does not apply to the estimated tax penalty, which has separate statutory exceptions instead.

Reasonable cause relief is not available for all penalties, and matching the argument to the penalty is a prerequisite rather than a detail. Each penalty draws its reasonable cause criteria from its own regulation, which is why the same explanation lands differently depending on what was charged.

The estimated tax exclusion is stated on the IRS reasonable cause page itself and is easy to miss. Requests for that penalty are routed to the underpayment of estimated tax by individuals penalty guidance, where the available exceptions are statutory rather than fact based. Building a reasonable cause narrative for it is effort spent on the wrong test.

The information return test deserves a note too, because it is genuinely different rather than merely stricter. It asks first whether the filer acted in a responsible manner both before and after the failure, which the IRS describes as requesting extensions where possible, trying to prevent a foreseeable failure, fixing the cause, and correcting the failure as quickly as possible. Responsible conduct alone is not enough. Significant mitigating factors or events beyond the filer's control have to accompany it, and the IRS lists first time filer status, a good compliance history, actions by the IRS, actions of an agent, and access to relevant business records among them.

One consequence of a successful request is often overlooked. The IRS charges interest on penalties, and it states that related interest is automatically reduced or removed when the underlying penalty is reduced or removed. The mechanics of that are described at interest. Interest on the underlying tax is a separate matter and follows its own rules.

How is a reasonable cause request made?

Two routes exist. The IRS can consider some requests by phone using the number printed on the notice, and it accepts written requests on Form 843. Phone consideration is limited to the failure to file, failure to pay, and failure to deposit penalties, and only below internal dollar thresholds.

The IRS says some penalties can be reduced or removed over the phone, using the toll free number at the top right corner of the notice, with supporting documentation on hand. It asks callers to have three things ready: the notice that was sent, the penalty at issue, and the reasons it should be removed.

What the public guidance does not spell out is how narrow that phone route is. The Penalty Handbook governs it through what it calls oral statement authority, and the boundaries are real. Oral and unsigned requests can be considered only for the failure to file, failure to pay, and failure to deposit penalties, and only where the amounts fall under internal thresholds. Everything else requires a written statement signed under penalty of perjury.

The manual also names categories that cannot be handled orally at all, regardless of amount: taxpayer identification number penalties, information return penalties, and penalties assessed by a compliance program. And where two or more penalties sit on the same module and any one of them exceeds the threshold or falls outside the three timeliness penalties, the manual instructs employees to ask for a single signed written request covering all of them rather than abating some by phone.

The written route runs on Form 843, Claim for Refund and Request for Abatement, which the IRS describes as the form for claiming a refund or requesting abatement of certain taxes, interest, penalties, fees, and additions to tax. The IRS also notes a sequencing quirk that works in the taxpayer's favor: where a caller asks for reasonable cause but the account meets the administrative waiver test instead, the IRS applies the waiver.

On content, the published instruction tracks the five questions from the manual. The IRS asks for an explanation of the facts and circumstances around the late return, deposit, or payment, covering what happened and when it happened, how the situation prevented timely filing or payment, and what attempts were made to file or pay.

• Hospital or court records, or a doctor's letter, to confirm illness or incapacitation, with start and end dates.
• Documentation of natural disasters or other disturbances.
• Copies of relevant written letters and the responses received.
• Copies of receipts, forms, or other documentation supporting the timeline.

Dates are the connective tissue in all of it. The manual tells reviewers that the dates and explanations should clearly correspond with the events on which the penalties are based, and that where they do not correspond, additional information should be requested. A narrative whose dates do not line up with the penalty period is the most common way a sympathetic set of facts still fails.

What happens when the IRS denies a reasonable cause request?

A denial has to arrive in writing and has to explain both the basis and the appeal route. The IRS allows a conference with its Independent Office of Appeals, generally within thirty days of the rejection letter, and Publication 4576 describes how that penalty appeals process runs.

The Penalty Handbook imposes a real obligation on the IRS here. Employees denying pre assessment relief or post assessment abatement must provide written notification of the denial and of appeal rights, regardless of whether the request arrived in person, over the phone, or in writing. The notice has to include a complete explanation of the decision and the basis for the denial, information on appeal procedures including how to submit a written protest, and power of attorney information.

Those denials arrive on standardized letters. The manual names Letter 854C, described as penalty waiver or abatement disallowed with appeals procedure explained, as the one generally used by campuses, along with Letter 852C and Letter 853C where the automated Reasonable Cause Assistant generated the determination. Recognizing the letter is useful, because it tells the reader that a decision was made rather than that a request was lost.

The appeal route is set out on the IRS penalty appeal page. It describes a conference or hearing with the Independent Office of Appeals, generally within thirty days from the date of the rejection letter, and it directs readers to the rejection letter itself for the specific deadline. The page lists four conditions that generally have to have occurred together.

1. 1.A letter arrived stating that the IRS assessed a failure to file or failure to pay penalty to an individual or business account.
2. 2.A written request asking the IRS to remove the penalty was sent.
3. 3.The IRS denied that request to remove the penalty.
4. 4.A letter denying the request arrived, which is the letter that conveys appeal rights.

The same page names the two penalties Appeals most commonly removes, failure to file and failure to pay, and points to Publication 4576 for an orientation to the penalty appeals process. It also points readers to the Penalty Handbook subsections on statutory exceptions and administrative waivers, which is the IRS suggesting that a denied reasonable cause request is worth re examining against the other two relief categories described at penalty relief.

None of this is a substitute for professional help. Representation before the IRS is the work of licensed practitioners, meaning attorneys, certified public accountants, and enrolled agents. A penalty large enough to matter, or one attached to a business or an examination, is the kind of situation where that help is commonly used.

Which IRS notices lead to a reasonable cause request?

Almost always a coded balance due letter. A CP14 opens the sequence with the first bill, the CP501 and CP503 reminders follow, and a CP504 raises levy intent. A CP161 carries a balance due on a business return. The code identifies which penalty is on the account.

Reasonable cause requests do not start in the abstract. They start when a letter arrives showing a penalty already charged, and the code printed on that letter says which penalty is at issue and how far the collection sequence has already advanced. That position shapes both the argument and the time available to make it.

• CP14 is the first balance due notice, and it is where a failure to pay penalty commonly first appears.
• CP501 and CP503 are reminder notices on a balance that remains unpaid.
• CP504 is a notice of intent to levy, which means the collection sequence has moved well past the first bill.
• CP161 shows a balance due, often on a business return, with penalty and interest included.

There is a genuine sequencing point buried in the codes. A reminder notice and a notice of intent to levy call for different urgency, and the collection track keeps moving whether or not a penalty relief request is pending. Where a balance cannot be paid at all, the relief question and the collection question are separate conversations, and the collection side is covered at the IRS hardship program.

One last point that applies across every version of this request. The IRS treats the obligation to comply as ongoing, and the manual says ordinary business care and prudence requires continuing to attempt to meet the requirements even though late. Filing a late return remains better than leaving it unfiled, and a request for relief on a return that was never filed at all is a request with a hole in the middle of it.