Sometimes you do not know whether you are owed a refund until something outside your control happens. A court rules in a case that affects your issue. Congress changes a rule retroactively. Another tax year's audit wraps up. A related party's case is decided. The problem is that the refund statute does not wait for any of those things. It keeps running.

A protective claim is the tool for that gap. It is a claim filed before the deadline that preserves your right to a refund if the contingency breaks your way. This guide explains what the IRS requires for one to count and how to use it.

What a protective claim is

The term protective claim does not appear in the Internal Revenue Code. The IRS describes it in its manual. IRM 25.6.1.10.3.2.5 says protective claims are filed to preserve the taxpayer's right to claim a refund when that right is contingent on future events and may not be determinable until after the statute of limitations expires. It says a protective claim is based on an expected change in the tax law, other legislation, regulations or case law.

IRM 21.5.3.4.7.3 describes them the same way: claims for credit or refund normally based on expected changes in a current regulation, pending legislation or current litigation. It adds that any claim based on a pending court case or decision is considered a protective claim, and that they are filed to protect the claimant's right to recover tax before the statute of limitations expires.

What makes it valid

Calling a document a protective claim does not make it one. IRM 25.6.1.10.3.2.5 says a claim should not be viewed as valid merely because the taxpayer labels it as such. It then sets out what a valid protective claim needs. It need not state a particular dollar amount or demand an immediate refund. But it must identify and describe the contingencies affecting the claim, it must be sufficiently clear and definite to alert the IRS to the essential nature of the claim and it must identify a specific year or years for which a refund is sought.

IRM 21.5.3.4.7.3.1 lists the same elements as processing requirements, adds that a protective claim must have a written component and tells employees to screen protective claims for statute timeliness and signatures.

The general claim rules still apply. Treasury Regulation 301.6402-2(b)(1) requires a claim to set forth in detail each ground on which a refund is claimed and facts sufficient to apprise the IRS of the exact basis, verified under penalties of perjury. A protective claim satisfies that rule by describing the contingency and the legal theory clearly, even if the amount is not yet known.

It has to be timely

A protective claim is only as good as its filing date. It must be filed within the period in IRC 6511(a), three years from the filing of the return or two years from payment, whichever is later. The guide to the refund claim deadline explains the period.

It is also subject to the same amount cap as any other claim. Under IRC 6511(b)(2), the eventual refund is limited to tax paid within the lookback window before the protective claim was filed. Filing the protective claim early locks in that window. The guide to the lookback limits covers how the cap works.

How the IRS handles it

IRM 25.6.1.10.3.2.5 says the IRS has discretion in deciding how to process protective claims and that, in general, it is in the best interests of the IRS and taxpayers to delay action on them until the pending litigation or other contingency is resolved. Once the contingency is resolved, the IRS may request additional information and then allow or disallow the claim.

So a protective claim usually sits. That is the point. It holds your place in line while the outside event plays out. When it resolves, you supplement the claim with the numbers.

There is one warning in the IRM. IRM 21.5.3.4.7.3.1 says that if the claimed amount is $1 or some other nominal amount when there is no valid condition, such as a pending event, and it is possible to determine the overpayment accurately, the claim may be rejected under no consideration procedures. A protective claim is for genuine contingencies, not a placeholder for work you could finish now.

When to use one

  • A court case is pending on a legal issue that, if decided favorably, would reduce your tax for an open year.
  • Legislation has been proposed that would apply retroactively to a year whose refund period is about to close.
  • A regulation is being challenged, or a change has been announced, that would affect a deduction or credit you did not claim.
  • Your refund for one year depends on the outcome of an audit or dispute for another year or another taxpayer, such as a related entity, and that matter will not resolve before your deadline.
  • You expect an amount you cannot yet calculate, such as a figure that depends on a third party's final determination.

In each case, the question is the same: will the refund period for the year close before you know whether you are owed money? If yes, a protective claim is worth considering.

Protective claims and amended returns

A protective claim is often filed on the same form as any amended return, but it serves a different purpose. An ordinary amended return asks the IRS to act now on facts that are known. A protective claim asks the IRS to hold the claim until an outside event resolves. Mixing the two causes confusion. If part of a refund is known today and part depends on a contingency, consider a regular claim for the known part and a clearly labeled protective claim for the contingent part, each stating its own grounds.

Remember that each claim stands on its own grounds under Treasury Regulation 301.6402-2(b)(1). A ground that appears only in a protective claim is preserved by that claim, and a ground that appears nowhere is not preserved at all.

How to prepare one

Use the form the regulations require for the type of tax: Form 1040-X for an individual income tax refund under Treasury Regulation 301.6402-3(a)(2), or Form 843 for claims not otherwise provided for under section 301.6402-2(c). IRM 21.5.3.4.7.3 says a protective claim can be identified by the literal words protective claim or by language describing the regulation, legislation or litigation the claim depends on, so label it clearly.

Describe the contingency specifically: name the case and court, the legislation or the related proceeding. Explain how a favorable outcome would produce an overpayment for each year listed. Identify every year separately, since section 301.6402-2(d) requires separate claims for each return and taxable period for income tax. Sign under penalties of perjury and file it in a way that proves the date.

Then calendar a follow-up. When the contingency resolves, send the IRS the computation and any additional facts it needs to process the claim.

The bottom line

Think of it as an insurance policy with a deadline. The premium is the time it takes to prepare a clear, specific claim. The payout is the right to a refund that would otherwise have expired while you waited for someone else's case to end.

A protective claim preserves a refund that depends on something you cannot control before the IRC 6511 deadline runs. To be valid under IRM 25.6.1.10.3.2.5, it must be written, describe the contingency, be clear enough to alert the IRS to the nature of the claim and identify the specific years. It must be timely, and the eventual refund is still subject to the lookback cap. File it before the window closes, then follow up when the outside event resolves.