Tax Planning for Net Operating Loss Carryback Elections – Houston Tax Attorneys


Congress has used Section 172 for net operating losses to stimulate the U.S. economy. It has done this by allowing certain losses to be carried back, thereby generating cash refunds to the taxpayer. This puts cash into the hands of taxpayers who are suffering losses. One only has to look at the history of changes to Section 172 to see this history.

One such allowance was for specified liability losses. These are losses that were specifically listed in Section 172 and allowed to be carried back to prior tax years. Environmental remediation costs were an example. When an oil and gas company has a drilling platform that needs dismantling or contaminated land requires cleanup, the tax loss can generate cash to help pay for these often extraordinary expenses.

The question hasn’t been clear in the various machinations of Section 172 is what happens when there are different loss carryback rules at play for a taxpayer in the same tax year. Can the taxpayer have two net operating loss carrybacks from the same tax year, to different prior years? The specified liability loss rules provide an example, as they had a 10 year carryback, whereas general losses had a two year carryback. So if a taxpayer incurred both in the same year, could they carry back 10 years and two years?

This brings us to Apache Corporation v. Commissioner, 2025 T.C. 11, which addresses this very issue. The tax court case provides important guidance on whether taxpayers can selectively waive certain carryback periods while preserving others–effectively being able to use NOL elections as part of their business and tax planning.

Facts & Procedural History

The taxpayer in this case is an oil and gas exploration and production company. For 2016 and 2017, the company filed consolidated corporate income tax returns showing net operating losses of approximately $1.9 billion and $3.1 billion respectively.

Buried within those massive losses were much smaller amounts that qualified as “specified liability losses” under Section 172(f)(1). In 2016, the taxpayer reported a specified liability loss of $40.7 million. In 2017, it reported $30.8 million. These amounts represented environmental remediation costs, decommissioning expenses, or similar cleanup obligations that qualify for special tax treatment.

The taxpayer made elections on both returns to waive the carryback period under Section 172(b)(3) for its consolidated net operating losses. But the taxpayer explicitly stated it was not electing to relinquish the carryback period for the specified liability losses. The company wanted to carry those environmental losses back the full ten years while carrying the regular losses only forward.

The taxpayer then filed Form 1139 applications seeking tentative refunds. It carried the $40.7 million specified liability loss from 2016 back to 2006, claiming a refund of $13.8 million. It carried the $30.8 million loss from 2017 back to 2007, claiming $10.1 million. The IRS issued both refunds.

Later, during an IRS audit, the government changed its position. The IRS issued a notice of deficiency for 2006 and 2007, disallowing the carrybacks entirely. The IRS’s position was that when the taxpayer elected to waive the carryback period, it waived everything. No cherry-picking allowed.

The taxpayer petitioned the U.S. Tax Court for redetermination. Both parties filed cross-motions for partial summary judgment on the carryback issue. The case was reviewed by the full court.

Net Operating Losses Under Section 172

Section 172 allows taxpayers to smooth income over time. When deductions exceed gross income in a year, the resulting net operating loss can be carried to other years. This prevents businesses from being overtaxed simply because their profitable and unprofitable years don’t align with the calendar.

The basic mechanism works like this. A net operating loss can be carried back to prior years to offset income that has already been taxed. This generates tax refunds–so cash paid to the taxpayer. Any loss remaining after the carryback can be carried forward to offset future income. The carryback provides immediate cash flow. The carryforward preserves the loss for future use.

Under the default rule in Section 172(b)(1)(A) that applied prior to 2022, net operating losses can be carried back two years and forward twenty years. The taxpayer starts by carrying the entire loss to the earliest possible year. If that year’s income doesn’t absorb the full loss, the excess carries to the next year, and so on until the loss is consumed or exhausted.

This default rule doesn’t work for everyone. Consider a company with significant research tax credits that are about to expire. If it carries losses back to years when it had those credits, the loss will eliminate the income. The credits then sit unused and eventually expire worthless. The company loses twice—once from the operating loss and again from the wasted credits.

Section 172(b)(3) addresses this problem. It allows taxpayers to elect to waive the entire carryback period and carry losses only forward. This preserves credits and other favorable attributes in the earlier years while banking the loss for future use. This is similar to rules that allow taxpayers to opt out of bonus depreciation, foregoe immediate expensing, etc.

The Ten-Year Carryback for Specified Liability Losses

Congress recognized that certain losses are particularly large and sporadic. Environmental cleanups don’t occur on predictable schedules. When they do occur, the costs can dwarf regular operating expenses. Limiting these losses to a two-year carryback often means the company can’t fully use them because income in just those two prior years won’t absorb the entire loss.

For the years in this case, Section 172(f)(1) defined specified liability losses to include two categories. First are product liability losses under subsection (A). Second are amounts under subsection (B) that satisfy liabilities under federal or state law for land reclamation, nuclear plant decommissioning, drilling platform dismantlement, environmental remediation, or workers compensation payments.

Under the rules applicable to these years, these losses must meet specific timing and accounting requirements. The deduction must arise from a liability that existed for a substantial period before the deduction year. The liability must be identified in financial statements or tax returns from earlier years. These requirements prevent taxpayers from manufacturing specified liability losses out of ordinary business expenses.

Section 172(b)(1)(C) grants specified liability losses a ten-year carryback period instead of the usual two years. This extended window gives companies a realistic chance to absorb the loss against income from more years. For businesses with cyclical earnings, reaching back ten years instead of two can mean the difference between using the loss fully or losing part of it forever.

The tax code treated specified liability losses as separate from the rest of a net operating loss. Section 172(f)(5) provides that for purposes of applying the sequencing rules in Section 172(b)(2), specified liability losses are treated as separate net operating losses to be taken into account after the regular portion. The taxpayer first carries back its regular loss two years, then separately carries back the specified liability loss ten years.

The law has changed since the years at issue here. The special treatment for specified liability losses described in this case no longer exists. The Tax Cuts and Jobs Act (“TCJA”) eliminated most net operating loss carrybacks effective for losses arising after December 31, 2017. Under current law, specified liability losses receive no special carryback period. They follow the general rule—no carryback at all, only carryforward. Losses can be carried forward indefinitely but are subject to an 80% limitation on the amount of taxable income they can offset in any given year. Congress provided temporary relief for losses arising in 2018, 2019, and 2020, allowing those losses a five-year carryback. But this temporary provision applied to all net operating losses during those years, not specifically to specified liability losses. The entire framework of extended carrybacks for environmental remediation costs, decommissioning expenses, and similar liabilities has been removed from the tax code.

Setting aside the policy argument for allowing specified liability loss carrybacks, this case is still relevant as to the broader statutory interpretation principles it establishes. The tax court’s analysis applies whenever Section 172(b)(1) provides multiple carryback periods for different types of losses in the same year. For example, farming losses currently receive a two-year carryback under Section 172(b)(1)(B). If Congress enacts future legislation creating additional special carryback periods for particular industries or types of losses, which it has done repeatedly over the years, the court’s reasoning would govern whether taxpayers can waive some carryback periods while retaining others.

The Election to Waive Carryback Periods

With that background, we can get into the election. Section 172(b)(3) states that any taxpayer entitled to a carryback may elect to relinquish the entire carryback period with respect to a net operating loss for any taxable year. The election has to be made by the due date of the return for the loss year. Once made, the election is irrevocable.

The statute uses specific language—”a carryback period” and “the entire carryback period.” Whether these terms refer to one unified period or potentially multiple periods becomes the central interpretive question. If Section 172(b)(1) establishes only one carryback period per loss, then the election necessarily applies to the whole loss. If it establishes multiple periods, then potentially the election could apply to each period separately.

Farmers and certain other taxpayers face similar questions. Section 172(b)(1)(E) allows eligible losses (including casualty losses and disaster-area losses) to be carried back three years. Section 172(b)(1)(F) allows farming losses a five-year carryback. Each of these provisions includes its own election mechanism allowing taxpayers to waive the extended carryback for that particular type of loss.

The question is whether Section 172(b)(3) works the same way. Can a taxpayer with multiple types of losses subject to different carryback periods waive some but not others? Or does the statute require an all-or-nothing choice?

The tax court held that taxpayers entitled to multiple carryback periods under Section 172(b)(1) may waive them individually. The court based this conclusion on statutory text, structure, judicial precedent, and the government’s own prior interpretation.

The tax court agreed with the taxpayer that reading Section 172(b)(3) as all-or-nothing makes little sense given the number of different carryback periods in Section 172(b)(1). Why would Congress grant taxpayers the flexibility to waive carrybacks entirely but then remove all flexibility to make nuanced choices when multiple carryback periods apply? Section 172(f)(6) provides another example of congressional flexibility. This provision allows taxpayers with specified liability losses to elect out of the special ten-year carryback and instead use the regular two-year carryback. A taxpayer might make this election if it had sufficient income in the two most recent years to absorb the loss and wanted to preserve attributes in earlier years. The existence of this additional election shows Congress wanted to give taxpayers choices about how to use these losses.

The Takeaway

This case confirms that the NOL rules can create multiple carryback years. Taxpayers can make elections to use their loss carrybacks strategically, which is what Congress likely intended. When a business has both regular operating losses and specified liability losses, for example, it can waive the short carryback period for regular losses while preserving the extended carryback for environmental and decommissioning costs. This flexibility allows companies to avoid wasting valuable tax attributes in recent years while still obtaining immediate refunds from the special losses. The same principles apply to other losses today. For example, a farm business with both farming losses (which get a two-year carryback) and other business losses could use the Apache framework to selectively waive carrybacks and preserve expiring credits or other tax benefits. This is another tool in the taxpayer’s tax planning toolbox.

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