Can Corporate Suspension Foreclose U.S. Tax Court Review – Houston Tax Attorneys


There are a number of administrative rules that businesses have to comply with. This can create administrative headaches for businesses–particularly small businesses.

The requirement for annual maintenace of state corporate status is an example. Businesses, particularly small businesses, often fail to meet annual state filing requirements. The result is that their corporate powers are limited. They then have to reinstate the entity, which in itself is another hassle.

State laws allow for businesses to retroactively fix these issues when there is a problem, so this is not a “gotcha” situation for them. But what about the IRS? Consider the example where the taxpayer owes the IRS and asserts is right to a collection due process hearing. Can the IRS have the hearing and then when the taxpayer petitions the tax court coming out of that hearing, not be able to bring suit in tax court due to state compliance issues?

The court addressed this fact patterin in Arbor Vita Corp. v. Commissioner, 166 T.C. No. 5. The corporation filed its tax court petition within the 30-day window while its California status was suspended, and eventually revived that status — but only months after the filing window for tax court had closed.

Facts & Procedural History

The taxpayer was a California corporation. It was formed in 1998. The California FTB suspended the corporation for failure to file certain California state tax returns. The business was legally disabled under state law.

For tax year 2017—several years earlier—the IRS had separately determined that the corporation failed to pay its unemployment tax liability. The IRS also assessed a civil penalty under tax code Section 6721 for the corporation’s failure to file Forms W-2, Wage and Tax Statement, with the Social Security Administration. These payroll tax disputes — employment taxes and associated reporting penalties — represent one of the more common types of federal liability that arise when a business is struggling to keep up with its obligations.

The IRS filed a notice of federal tax lien (“NFTL”) against the corporation. The corporation contested the lien filing by timely requested and participated in a collection due process (“CDP”) hearing before the IRS Independent Office of Appeals. Appeals sustained the lien filing in a Notice of Determination in 2025.

The corporation then filed a petition in the U.S. Tax Court — within the 30-day window. Its California corporate status remained suspended at that point. The FTB did not issue a Certificate of Revivor until more than five months after the Notice of Determination issued and well after the 30-day filing window had closed. The IRS moved to dismiss the tax court proceeding for lack of jurisdiction on the ground that the corporation lacked the capacity to maintain the proceeding.

Taxpayer Collection Due Process Rights

When the IRS pursues collection of unpaid tax debts through a federal tax lien or levy, the tax code gives taxpayers the right to contest that collection action before it proceeds. This is a fundamental right that is intended to satisfy the Constitutional right to be heard prior to taking of property.

Section 6330 requires the IRS to provide notice and an opportunity for a CDP hearing before the IRS Office of Appeals. At that hearing, the taxpayer can challenge the appropriateness of the collection action, contest the existence or amount of the underlying liability in certain circumstances, and raise collection alternatives such as installment agreements or offers in compromise.

Appealing IRS collection actions through the CDP process is often a great way to pause collection activity and negotiate a resolution. Section 6320 governs CDP rights in the context of tax liens. Section 6330 covers levies. Both sections provide for judicial review of an adverse determination by Appeals, but both also require a timely petition.

The 30-Day Window to Petition the Tax Court

If the case is not resolved in the taxpayer’s favor, generally, the administrative portion of the CDP hearing ends when the IRS issues a Notice of Determination.

After the IRS issues a Notice of Determination sustaining a collection action, the taxpayer has 30 days to file a petition for review in the U.S. Tax Court. This deadline comes from Section 6330(d)(1). Missing the window has historically meant no further judicial review, and the IRS can proceed with its collection activity.

For many years, courts treated the 30-day deadline as jurisdictional for the tax court. A jurisdictional deadline is one whose violation deprives the court of all authority to hear the case — no exceptions, no equitable relief. Missing it was fatal, full stop. That framework changed in 2022.

In Boechler, P.C. v. Commissioner, 142 S. Ct. 1493 (2022), the Supreme Court held that the Section 6330(d)(1) deadline is not jurisdictional. It is an ordinary, nonjurisdictional deadline subject to equitable tolling. The distinction matters. A nonjurisdictional deadline may be extended in appropriate cases where the taxpayer demonstrates diligence and extraordinary circumstances outside its control. We’ll address it further below, but the Boechler decision also has a downstream effect on the corporate capacity question in this case.

Corporate Capacity: Tax Court Rule 60(c)

Before getting into Boechler further, we have to consider tax court Rule 60.

The U.S. Tax Court is a court of limited, legislatively granted jurisdiction. It often notes its own limitations in cases–even though other courts who review its cases on appeal do not always agree that the tax court’s jurisdiction is so narrrow. But even then, the tax court can only hear cases that Congress has specifically authorized.

This brings us to Tax court Rule 60(c). This rule provides that the capacity of a corporation to engage in litigation before the court is determined by the law under which the corporation was organized. For a California corporation, California law governs the capacity question — not federal law. Like most other states, a corporation that lacks legal standing under California law at the time the jurisdictional or filing requirements are met cannot maintain a proceeding in the tax court.

Equitable Tolling for a Timely-Filed Petition

This brings us back to this case. The taxpayer filed its petition in late April of 2025. Its California corporate status was suspended at that time. The 30-day window under Section 6330(d)(1) expired in early April 2025 — 30 days after the March 2025 Notice of Determination.

When that window closed, the IRS acquired a statute of limitations defense. The corporation did not revive its California status until September of 2025, more than five months after the deadline had passed.

Following Boechler, the suspension at the time of filing did not automatically bar the petition, because Section 6330(d)(1) is a nonjurisdictional, procedural deadline. California’s relation-back doctrine could theoretically apply. The problem was Section 23305a. Retroactively validating the petition at that point would directly prejudice the Commissioner’s limitations defense — a defense that had fully accrued before revival occurred. The tax court declined to override that accrued defense.

The taxpayer argued that California courts have allowed retroactive validation of a notice of appeal filed by a suspended corporation. The tax court rejected this analogy on two grounds. First, an expired statute of limitations constitutes an accrued defense under Section 23305a, whereas the expiration of a time limit for filing a notice of appeal does not carry the same defense-accruing effect under California law.

Second

Second, the tax court noted that it is not an appellate court. The Supreme Court has characterized the tax court’s role as closely resembling that of the federal district courts and not as an appellate tribunal. There was no principled basis for treating a tax court petition as a notice of appeal, and the court declined to create one.

As a fallback argument

As a fallback argument, the taxpayer asked the tax court to apply equitable tolling to the 30-day deadline. Because Boechler established that the deadline is nonjurisdictional, it would seem that equitable tolling is available under Section 6330(d)(1). To obtain it, a taxpayer only has to show that it pursued its rights diligently and that extraordinary circumstances outside its control prevented it from filing on time.

The court disposed of this argument with a simple observation: equitable tolling extends a deadline that was missed. The taxpayer here did not miss the deadline. It filed its petition on time. There was no extension to grant. The taxpayer’s problem was not that it filed late — it was that it filed without legal capacity, and its revival came after the window closed. Equitable tolling has no mechanism to address that circumstance because there is no expired deadline to extend.

But with that said, is this a moot issue? Can the taxpayer can simply file a second petition now, and again assert equitable tolling? It would seem that this is the remedy and could put the matter before the court again.

The Takeaway

The outcome in this case shows that there is a convergence of California corporate law and federal tax procedure that can catch even well-advised businesses by surprise. The Boechler decision created genuine flexibility for California corporations that file timely CDP petitions while suspended — so long as revival occurs before the 30-day window closes.

According to this case, the moment the window expires before revival, that flexibility disappears. The IRS acquires an accrued limitations defense, and California’s Section 23305a gives that defense protection against retroactive override. For any California business simultaneously dealing with state tax compliance failures and federal collection actions, these two clocks run concurrently and entirely independently of each other. Resolving the state compliance problem first — or at minimum within 30 days of an adverse CDP determination — is not advisable. This can help avoid having to file multiple tax court petitions.

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


What is Azure Application Insights?

Application Insights is an Application Performance Management (APM) service for developers to monitor live applications. The anomalies in performance are automatically detected. It also includes powerful analytics tools that help in diagnosing issues. The insights help to understand how users are interacting with the application. With the Application Insights, developers can continuously improve performance and usability.

Application Insights works on applications built with various languages like .NET, Node.js, Java, and Python. The applications can be hosted on-premise or on the cloud, or hybrid. It can integrate with DevOps processes. It also integrates with Visual Studio App Center and can monitor telemetry from mobile apps.

All the data in the Application insights service can be exported to a database or any external tools. Application Insights SDKs are available for web services hosted in ASP.NET servers, Java EE, Azure. They are also available for web clients, desktop apps, mobile devices like Windows Phone, iOS, and Android.

How does it Work?

To monitor your application, all you have to do is enable the Application Insights from the Azure portal or install a small instrumentation package (SDK) in your application. The application will be monitored by this instrumentation package. It will use a unique GUID, which is also known as an Instrumentation Key, to direct the telemetry data to an Application Insights resource. 

IMAGE

Since we install the instrumentation package in the application, it doesn’t have to be hosted on Azure. The application can run anywhere. We can instrument any background components of an application and the JavaScript in the web pages too. Application Insights can also collect telemetry data from Azure diagnostics, Docker logs, or performance counters when they are integrated into Azure Monitor. 

Interested in learning Azure Course ? Enroll in our Microsoft Azure Certification Training program now!

What does the Application Insights Monitor?

Application Insights focuses on the performance of an application to ease the work of the development team. It monitors the following constraints,

  • Request rates, response times, and failure rates – It tells us which pages are being visited the most and at what times of the day.
  • Dependency rates, response times, and failure rates – It shows any external sources that might slow the application down.
  • Exceptions – It reports both server and browser exceptions. It gives an aggregate statistics of all the instances. We can further drill down to get statistics of individual instances.
  • It will also monitor the page views and load performance collected from the user’s browser.
  • It monitors AJAX calls from web pages, users, and session counts.
  • It will show the performance of memory, CPU, and network usage.
  • We can get host diagnostics from Docker or Azure.
  • We can correlate events with requests using the diagnostic trace logs of the application.
  • It also shows the custom events or metrics that the developer includes in the code.

Uses of Application Insights

Once we install Application Insights for an application, we can get the following benefits.

  • The load, responsiveness, and the performance of page loads, dependencies, AJAX calls can be known through an intuitive application dashboard.
  • We can identify the slowest requests and determine the requests that are failing often.
  • When a new release of an application is deployed, the statistics of it can be seen through a live stream.
  • If users are affected, we can get an alert so we can check how many users are being affected.
  • If there are any request failures, we can correlate them with the exceptions, dependency calls, and traces.
  • When a new feature of the app has to be deployed, we can measure the effectiveness of it.

Microsoft Azure Certification Training

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

Limitations of Azure Application Insights

Like any other solution, Application Insights has some limitations.

  • If your code uses dynamic SQL, the Application Insights collects the full query into Azure, which might result in uploading sensitive data contained in the query.
  • The reports show up to the server and database level. But it cannot monitor individual SQL queries on how long they are being executed.
  • When you add Application Insights and deploy the application to Azure, it won’t collect the SQL queries unless a site extension is installed for it.
  • It cannot collect first chance exceptions.
  • It cannot show common exceptions across all applications.
  • If you are using ASP.NET for your application, Application Insights does not support asynchronous HttpClient calls.
  • There is no alert severity specified.
  • We cannot configure alerts to go to specific distribution lists based on severity.

Data collection, retention, and storage of Application Insights

When Azure Application Insights SDK is installed in your application, it starts sending telemetry data from your app to the cloud. Each SDK uses different techniques to collect telemetry data from different kinds of applications. You can also include custom telemetry to send your data. Azure runs some processes called availability tests to web applications regularly. The results from the test will be sent back to the Application Insights service.

You can test which data is being sent by the SDK. You can view the data in the output windows of the IDE and browser while testing the application. The data in the Application Insights service can retain up to 730 days. Users can set up a retention duration. The debug snapshots are stored for 15 days in the Application Insights service.

If the SDK is not able to reach the endpoint, the telemetry channels store the data in local storage temporarily by creating temp files. Once the issue is resolved, the new data, along with the persisted data, will be sent to Azure by the telemetry channel.

Do you want to collaborate in the Application Packaging and Virtualization world? Begin by learning Application Packaging and Virtualization Training!

HKR Trainings Logo

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

Enable Application Insights for your Application

Create Application Insights Service

Navigate to the Azure portal at https://portal.azure.com/ and login to your account. Click on ‘+ New’ from the left side menu. Search for ‘Application Insights’ in the search bar. You can see the service in the search results. Click on it to open the service and click on ‘Create’. Give a name for your service, select your application type from the drop-down menu, and select your subscription. Choose ‘Create new’ for the ‘Resource Group’ field and give the same name that you gave for the service. Select a location and click on ‘Create’.

                                         Learn new & advanced  Architect solutions in hkr’s  Azure Architect solutions course

Go to the newly created resource group and click on ‘app insights resource’. You will get the details of the resource. Copy the ‘Instrumentation Key’ from the page.

Add the Instrumentation key to the Application

Open Visual Studio and navigate to the appsettings.json file of your application. Add the below code in the file.

"Application Insights": {
"InstrumentationKey": "Your_instrumentation_key"
}

Replace the ‘Your_instrumentation_key’ with the one you copied before. It appears as a NuGet package. Go to the package.json file in your application, and you can see the Application Insights package added. You have successfully configured Application Insights to your application.

View the telemetry data

Launch the application from Visual Studio and play around with it. Stop the application. Right-click on the application, select ‘Application Insights’, and select the ‘Search Debug Session Telemetry’ option. You can see the telemetry data captured by your application. You can also see the details in Application Insights. Right-click on the application, select ‘Application Insights’, and select the ‘Open Application Insights Portal’ option.

The Application Insights portal opens up, and you can see the telemetry data collected from your application. You can drill down to see the page load metrics and more.

Microsoft Azure Certification Training

Weekday / Weekend Batches

Conclusion

Application Insights is a simple way for developers to detect and diagnose application performance issues of live applications. The SDKs vary for different applications and different platforms. Each SDK component sends different data. So choose one that is suitable for your application and install it. You can also include code in your application to send unhandled exceptions. The Azure Application Insights has a built-in map feature that can be used to identify the performance of dependencies.



Source link