You Can’t Raise What You Didn’t Know: The Variance Doctrine – Houston Tax Attorneys


Our income tax system uses a self-reporting process. Taxpayers, in most cases, voluntarily file income tax returns. The IRS can then evaluate the filings to determine whether they appear to be correct or warrant further investigation.

The IRS has developed a whole regime of forms to be used for this very purpose. Taxpayers who fill those out are, in theory, providing all of the information the IRS needs to evaluate whether the information reporte is correct.

The exception to this is for refund claims. Refund claims have a small box, consisting of a few lines, where taxpayers can write out an explanation for the basis of their refund claim. Despite only having a small box to write, the IRS takes the position that any theory not put forth in the small box means that the theory cannot be raised–at least that is the case when it comes to tax litigation.

So imagine that you filed a refund claim as you overpaid your taxes for a particular year and you want your money back. You do your best to fill out the small box that is provided for the “explanation.” Then after that, you discover additional facts that would have changed the text you put in the small box for the explanation. After bringing suit in tax court, the IRS moves to dismiss because the information that you did not know at the time you filled in this small box on the amended return was not listed in the small box.

This is the situation in the Salta v. United States, No. 24-254 (2d Cir. Oct. 6, 2025) case. The appeals court was tasked with deciding whether the information in the small box that was not known at the time had to be there for the litigation to proceed.

Facts & Procedural History

This case involves a common scenario–a foreclosure. In January 2015, the taxpayer-husband’s property in was in foreclosure. Rather than proceed through a lengthy foreclosure process, the taxpayer signed a deed-in-lieu-of-foreclosure arrangement. He transferred the deed to the mortgagee. In exchange, the mortgagee and loan servicer agreed to waive their rights to pursue a deficiency judgment against him.

On their 2015 joint tax return, the couple reported $113,087 in cancellation-of-indebtedness income from the discharge of the husband’s mortgage debt. They paid the tax on this income. Years later, they filed a refund claim to request a refund from the IRS because they believed the cancellation-of-indebtedness income should have been taxable in 2017 rather than 2015.

The IRS denied their refund request. Romeo and Phyllis then filed a refund suit in federal district court. The government moved for summary judgment. The taxpayers cross-moved for summary judgment. At this point in the tax litigation, they raised a new argument. The January 2015 Relocation Agreement was never enforceable because the mortgagee never signed the documents. Furthermore, the loan servicer lacked power of attorney to act on the mortgagee’s behalf.

The district court granted summary judgment for the government. The court found that the variance doctrine barred the taxpayers from raising their unenforceability argument because they had not presented this theory in their administrative refund claims. That resulted in the current court opinion.

When Debt Forgiveness Creates Taxable Income

The tax code treats income from discharge of indebtedness as taxable income under Section 61(a)(11). This provision makes sense as a matter of tax policy. When a lender forgives debt, the borrower experiences an increase in wealth. The borrower no longer has an obligation to repay money that was previously owed.

The timing of when this income must be recognized matters for income tax purposes given that our income tax system follows a strict year by year measurement process. Recognizing income in the wrong year can affect the applicable tax rates, impact the availability of deductions and credits, etc. It can also affect the statute of limitations for assessment. Getting the year wrong means paying tax when you shouldn’t have to. Then you face the burden of fighting to get that money back.

The court have explained that debt discharge creates taxable income in the year the discharge occurs. But determining exactly when a debt is “discharged” for tax purposes isn’t always straightforward.

The general rule is that debt is viewed as having been discharged the moment it becomes clear that tbe debt will never have to be paid. Any identifiable event which fixes the certainty of the discharge may be taken into consideration. This standard focuses on certainty and identifiable events. A vague possibility that debt might not be collected often isn’t enough. The taxpayer has to show a specific moment when it became definite that the debt would not have to be repaid.

The appeals court in this case found that the January 2015 deed-in-lieu arrangement constituted an identifiable event discharging his mortgage debt. The Relocation Agreement and related documents showed that the mortgagee accepted the property “as full satisfaction for the amount owed on the mortgage loan.” The documents explicitly stated that the taxpayer’s consideration for the deed transfer included “the full cancellation of all debts . . . [and] obligations . . . secured by” the mortgage.

This seemed like a straightforward application of the rules. An identifiable event occurred in January 2015 that made it clear the taxpayer’s mortgage debt would never have to be paid. Therefore, it seemed like 2015 was the proper tax year for recognizing the cancellation-of-indebtedness income.

The Variance Doctrine: You Must Raise Every Argument Administratively

This brings us to the variance doctrine. This applies to refund claims that are litigated as tax refund claims.

Before bringing a refund suit in court, taxpayers have to first file an administrative claim for refund with the IRS. This requirement is in Section 7422(a) of the tax code. This is intended to give the IRS an opportunity to correct errors administratively, create a record of the claim, and, ultimately, define the scope of any later litigation.

The variance doctrine builds on this administrative exhaustion requirement. Under this doctrine, taxpayers may not raise different grounds in their refund suit than those they brought to the IRS in their administrative claim. The courts have explained this as thge taxpayer having to advance in the administrative proceeding any contention it wishes to pursue in court.

The courts have articulated several rationales for the variance doctrine. The Sixth Circuit explained in McDonnell v. United States, 180 F.3d 721 (6th Cir. 1999), that the purpose is “to prevent surprise, and to give the IRS adequate notice of the claim and its underlying facts so that it can make an administrative investigation and determination regarding the claim.”

This makes sense in most cases. The IRS shouldn’t have to defend against entirely new theories that appear for the first time in litigation that would change the outcome of the litigation. The IRS should have an opportunity to investigate and resolve claims administratively. But what about when the facts are not known to the taxpayer or the IRS? That is what this court case and this article is about.

The “Should Have Known” Trap

The taxpayer argued they couldn’t have raised the unenforceability theory in their administrative refund claims because they only discovered years later that the mortgagee never signed the documentation. They argued that this created an exception to the variance doctrine.

The appeals court rejected this argument on two grounds. First, the court noted that the taxpayers cited no legal authority establishing an exception to the variance doctrine where a taxpayer learns after filing a refund request that a private contract may have been unenforceable. The court stated it was “aware of none.”

Second, the court held that the taxpayers “knew or reasonably should have known the facts underlying their unenforceability theory back in January 2015.” The court based this conclusion on the face of the documents themselves. The Relocation Agreement had no place for the mortgagee to sign. When the husband signed the Agreement in Lieu of Foreclosure and the Terms of Release of Premises, it was allegedly “clear from the face of the documents that the mortgagee had not signed them.”

Moreover, the court opinion notes that the taxpayer-husband asserted that he didn’t learn until discovery in the refund action about the loan servicer’s “lack of a power of attorney” to act on the mortgagee’s behalf. This is not information that would be apparent from the face of the documents.

The court created an impossibly high standard, partciularly for unsophisticated taxpayers. The majority of homeowners dealing with mortgage servicers during a foreclosure would naturally assume the servicer has authority to act on behalf of the mortgagee. Homeowners don’t typically scrutinize signature blocks to determine whether their lender signed or only the servicer signed.

More fundamentally, the absence of a signature line for the mortgagee doesn’t necessarily signal anything unusual. Many contracts are structured to be signed only by certain parties. The loan servicer’s signature might well have been sufficient if the servicer actually possessed proper authority.

Filing Kitchen-Sink Refund Claims

Consider a taxpayer who files a refund claim based on one good-faith theory supported by known facts. Later, during discovery or further investigation, new facts emerge that support a completely different and stronger argument. That taxpayer is stuck with the original theory. The better argument is barred by the variance doctrine because the taxpayer “should have known” the facts supporting it.

Given this case, to preserve all possible arguments, taxpayers have to consider filing administrative claims that raise every conceivable theory. This includes theories that seem speculative or unsupported by facts known at the time.

This forces taxpayers to recommend the filing of protective claims that read like litigation complaints. A refund claim might need to argue simultaneously that a contract was valid and enforceable (supporting one theory) while also arguing that the same contract was void and unenforceable (supporting another theory). These contradictory positions must both be asserted simply because the facts might develop either way.

Importantly, this approach negates the practical reasons for the variance doctrine. This approach wastes IRS resources and would not give the IRS easy to access information to decide whether to investigate the claim. The IRS has to evaluate and maybe investigate and respond to kitchen-sink claims rather than focusing on the taxpayer’s actual good-faith basis for the refund. This makes the identification of claims worthy of investigation even more difficult for the IRS, not less difficult.

The Takeaway

This case points out a trap for those filing refund claims when the facts are unknown. It shows that procedural doctrines can defeat substantive tax claims even when the taxpayer may be right on the merits. The court’s strict application of the variance doctrine combined with its “should have known” standard creates a nearly impossible burden for taxpayers who discover new facts after filing administrative refund claims. The decision fundamentally changes how taxpayers have to approach refund claims and amended tax returns when dealing with IRS audits and adjustments. Filing a focused refund claim based on a single well-supported theory is no necessarily the route to go. Instead, one may need to consider filing comprehensive claims raising every conceivable argument regardless of how speculative those arguments may be. This prevents being barred from raising theories later if new facts emerge, even though this approach benefits neither taxpayers nor the IRS.

Watch Our Free On-Demand Webinar

In 40 minutes, we’ll teach you how to survive an IRS audit.

We’ll explain how the IRS conducts audits and how to manage and close the audit.  



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Expedite your Tibco Business events with our recently designed HKR’s Tibco Business Events Interview Questions with answers. This blog is specially designed under the guidance of the SME team to help the fresher as well as experienced professionals. The Tibco Business event is one of the popular business tools to offer complex event processing or CEP. As the Tibco business events market is growing like anything and you can expect huge job openings across the world. As per the latest research, almost 0.67% of the software products are developed on the basis of Tibco business events tools.

Most Frequently Asked Tibco BE Interview Questions

What is the Tibco business event tool?

Ans: Tibco business event is a popular tool used to process any complex business events. These business events in software systems are later used to predict any business changes and to perform in a better way.

Become a  Tibco BE Training Certified professional by learning this HKR Tibco BE Training!

What are the key features of using Tibco Business Event?

Ans: Below are the important key features of using Tibco Business event;

  • Tibco business event is a high-performance event processing platform for applications that are used to monitor, analyze, and respond to parallel event streams.
  • Tibco business event extreme drivers deliver dramatic new levels of performance, scalability, and robustness for demanding complex event processing (CEP) and real-time event-driven applications.
  • This platform automatically manages consistency for efficient parallel processing and high vertical scalability.
  • A hybrid rules and java programming model enables applications to maximize the capabilities of languages, seamlessly share data and events.

What is the role of channels and destinations in the Tibco Business event?

Ans: Channels are nothing but resources used to establish the connectivity and communication between various business events. The events are like JMS sources, RV sources, and HTTP sources.

Destinations are specified with channels and explain the source and sink for the Tibco business messages.

Mention the product compatibility used in Tibco Business events?

Ans: The Tibco business Events Extreme data grid feature is compatible with Tibco Active spaces enterprise edition version 2.0.2 hot fix 9.

What are the packages installed in the Tibco business event?

Ans: Below are the important packages installed in Tibco Business events such as;

  • rpm –q compat-expat1 –compat-expat1-1.95.8-8.el6.x86_64
  • rpm-q pstack –pstack-1.2-7.2.2
  • rpm –q gdb –gdb-7.0.1-42.el5.
  • rpm –q sysstat –sysstat-7.0.2-11.e15

Tibco BE Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning

 

Explain the hardware required to install the Tibco business event?

Ans: Below are bowsers which are supported;

1. Chrome 16

2. Firefox 9

3. Internet Explorer 9

4. Safari 5

The disk space and memory requirements;

Disk space – 4 Gb

Memory – 2 Gb RAM

Java compatibility:

Tibco business event uses the two JRE versions:

1.7.0_45 –default JRE

1.6.0_30.

How events are generated in the Tibco Business event?

Ans: The events can be generated in Tibco business event using instance created on the base of input channels.

What do you mean by RMS and mention its uses?

Ans: RMS is also known as Rule management Server this is a business event component. This is used to manage decision projects and also provides various mechanisms.

  • This RMS offers user authentication, authorizing project decisions, and also consists of project management features.
  • This RMS enables the decision manager to communicate the rule management server and also helps users to check project decisions, decision tables of local copies, and commit changes.

How can we prioritize and de-prioritize rules for a business event?

Ans: In the Tibco business event tool, to perform a specific event, users can have multiple event rules. The rule priority value can be decided on the base of the sequence where rules are triggered. The value which is closer to 1 means that we can have a higher priority.

. Describe the flow messages used in the Tibco Business event?

Ans: Steps:

1. In the Business events the messages will be received through various channels along with appropriate destinations.

2. At first, the event preprocessor will be executed.

3. Here all the incoming messages will be converted to business events.

4. Rules will be triggered on the basis of these available events.

. What is CDD and what’s its significance?

Ans: CDD stands for Cluster deployment description, this is an XML file. This file consists of required information related to the deployment of the Tibco business event project.

. Why scorecards are used in the Business event?

Ans: Scorecards are a type of concept used in business events. Scorecards are sometimes used as a static variable in various programming languages, this scoreboard offers project-wide scope and single instance. These scoreboards are used to keep track or store the information which is later used throughout the project interference agent.

. Mention the steps involved in the Tibco business event installation process?

Ans: The steps included are;

1. Installation guide -> this gives complete installation information

2. Application Architect’s guide -> this consists of details like architectural details or rule programming.

3. Application Developer’s guide -> this consists of details like programmer documents used in rule programming.

4. Decision manager user’s guide -> this gives details like user documentation and decision tables information.

5. Web studio user’s guide -> consists of user documentation available on Web studio.

6. Architect’s guide -> Consists of architectural details on the application platform.

7. Java developer’s guide -> Contains whole java programmer documentation

8. Performance tuning guide -> Application performance documentation which holds tuning information.

9. System guide -> which consists of machine resources information for the application.

10. Code snippets -> source code for the programming snippets and java developer’s guide.

. Mention the difference between Tibco BW and Tibco BE?

Ans: Tibco BW is also known as the information bus company warehouse tool. This is an information, integration, and analytical tool. Tibco BW software is used to manage, integrate, and monitor the business level enterprise tool. This is widely used because of its flexibility, scalability, and reliability.

Tibco BE is a tool used to process complex business events. These business events are used to predict any business changes and enable them to perform in a better way.

. What is an event preprocessor and explain?

Ans: An event preprocessor is the same as a rule function. This type of rule function is used to process any incoming messages before these messages are converted into business events.

. What is the relationship between decision tables and virtual rule functions?

Ans: Decision tables are considered as an implementation for virtual rule functions. And virtual rule functions consist of one or more decision tables.

Final words:

I hope I have tried my best to explain the very important Tibco Business event interview questions and answers. Learning only this article is not enough to get into top companies. You should have a thorough knowledge of industry-based projects, to become a master in this tool please visit our website www.hkrtraining.com.

. Define Rules and how TIBCO BE rules work.

Ans: Rules in TIBCO BE state the actions that need to be taken on specific conditions. Moreover, rules will activate when specified conditions are met based on events.

HKR Trainings Logo

Subscribe to our YouTube channel to get new updates..!

. What is the use of TIBCO BE Concepts?

Ans: The concepts are built to hold any entity’s properties. In the Rules and Rules Functions, Concepts’ instances are often produced using data from the events.

. What is the use of Routers?Ans. Routers help move messages between the different EMS servers.

Ans: Routers help move messages between the different EMS servers.

Related Article: Tableau Prep Training

. List out the various acknowledgement modes in TIBCO EMS.

Ans: These acknowledgement modes available in TIBCO EMS for message delivery included.:-

  • Auto
  • Client
  • Explicit
  • Dups_ok
  • Transitional
  • No_ack

. What is the way to Configure a Client for Fault Tolerant Connection?

Ans: Here, it needs to mention different servers as a comma-separated list of various URLs, and both URLs should use the same protocols. Such as TCP or SSL. 

. Name the various messages used in EMS.

Ans: The following types of messages are used in EMS.

  • Text
  • Stream
  • Bytes
  • Simple
  • Map
  • Object 
  • XML Test

. How can we develop RESTful Web Services in TIBCO?

AnsTIBCO offers a plugin for JSON and REST, which help develop RESTful Web Services within TIBCO Designer.

. Define the process of integrating TIBCO BE with TIBCO BW.

Ans: Based on the configured channel type in TIBCO BE, you can easily send messages to TIBCO BW and get responses. For example, if TIBCO BE configures a JMS channel, you can send JMS messages to specific destinations from TIBCO BW. Then you will get a response through the Recieve JMS Message activity.

. What does a Flow Control Property state in TIBCO?

Ans: It states the maximum size of messages pending on the server.

. Name the storage methods used in TIBCO EMS Server.

Ans: There are two storage methods- Database and File Based.

. Mention the various Delivery modes supported by TIBCO EMS.

Ans: The following are the various delivery modes that TIBCO EMS supports:-

  • Persistent
  • Non-persistent
  • Reliable

Tibco BE Training

Weekday / Weekend Batches

. Define Shared State in the fault-tolerant operations in TIBCO.

Ans: In TIBCO, the fault-tolerant servers connect with Shared State, which includes persistent messages and client information.

. Distinguish between Rendezvous (RV) and EMS.

Ans: Both are different products and have different architectures. TIBCO EMS uses a client-server architecture, and RV uses distributed architecture. Further, EMS uses the TCP protocol, whereas RV uses the TRDP protocol offered by TIBCO. In EMS, the producer sends messages to the central server, whereas in RV, the producer directly sends messages to the consumer.

. What is meant by Fail Safe in TIBCO BE?

Ans: The Fail Safe attribute controls whether the server writes persistent messages asynchronously or synchronously to the disk. Also, the messages sent are securely stored on the disk before they are sent. It ensures that no messages are lost.

. What is the Message size that TIBCO EMS supports?

Ans: The maximum message size that TIBCO EMS supports is 512MB.

About Author

author-image

Kavya works for HKR Trainings institute as a technical writer with diverse experience in many kinds of technology-related content development. She holds a graduate education in the Computer science and Engineering stream. She has cultivated strong technical skills from reading tech blogs and also doing a lot of research related to content. She manages to write great content in many fields like Programming & Frameworks, Enterprise Integration, Web Development, SAP, and Business Process Management (BPM). Connect her on LinkedIn and Twitter.

Upcoming Tibco BE Training Online classes

Batch starts on
30th Apr 2026
Mon & Tue (5 Days)
Weekday
Timings – 08:30 AM IST
Batch starts on
4th May 2026
Mon & Tue (5 Days)
Weekday
Timings – 08:30 AM IST
Batch starts on
8th May 2026
Sat & Sun (6 Weeks)
Fast Track
Timings – 08:30 AM IST



Source link