What If You Don’t Show Up to Your CDP Hearing? – Houston Tax Attorneys


You get a Final Notice of Intent to Levy for a year that you don’t feel that you owe the tax. The IRS made a mistake.

You file the Form 12153 to request a Collection Due Process hearing because that’s what the letter says to do. The IRS assigns a settlement officer. She sends you a letter asking for a Form 433-A, bank statements, missing returns, and proof of estimated tax payments.

Then you go quiet. You ask to reschedule the call. You don’t return calls. You don’t send the documents. You finally call in but tell the settlement officer the case should wait for an appeal in a different tax year. The hearing ends. The IRS sustains the levy.

Now what? Can you walk into U.S. Tax Court and have a judge take a fresh look at the tax bill? Or have you already lost your shot?

The recent decision in Menge v. Commissioner, T.C. Memo. 2026-41 (May 19, 2026), addresses what happens when a taxpayer requests a CDP hearing but does not engage with the IRS Appeals process.

Facts and Procedural History

The taxpayer had unpaid tax balances for back taxes owed to the IRS for the 2015 through 2018 tax years. He had filed his tax returns. He just hadn’t paid the tax he reported as being owed.

The IRS sent a Final Notice of Intent to Levy. The taxpayer responded by timely requesting a Collection Due Process hearing on Form 12153 and checking the box indicating he could not pay the balance. This is one of the ways to get the IRS to agree to a collection alternative, like an installment agreement, currently not collectible status, or an offer in compromise.

Eventually a settlement officer was assigned. She did what settlement officers do. She verified the assessments by checking the IRS’s records, scheduled a hearing, and sent the taxpayer a letter asking for the documents she needed to evaluate any collection alternative. The list included Form 433-A, three months of bank statements, a corrected 2016 return, signed returns for 2020 and 2021, and proof of estimated tax payments for 2022.

The taxpayer’s response was to ask for the Administrative Record and to postpone the hearing. The case was reassigned to a second settlement officer. The second officer sent the same document request and scheduled a new hearing. The taxpayer asked to delay. The request was denied. The taxpayer did not show up and did not send any documents.

A month later he left a voicemail saying the years at issue were also pending before the U.S. Tax Court and the First Circuit. The second settlement officer returned the call and explained that the cases on appeal did not involve any of the tax years in this hearing. The hearing was rescheduled. The taxpayer called in this time. But when the settlement officer told him he needed to submit the requested information to challenge the underlying tax, the taxpayer just repeated his argument that he was owed a refund from 2013 that should be carried forward.

Apparently the 2013 tax year had already been litigated and lost in the U.S. Tax Court and then again in the First Circuit. It had nothing to do with the four years on the levy notice, even if the taxpayer felt that he was owed a refund that carried forward.

After the hearing, the taxpayer sent nothing further. The settlement officer issued a Notice of Determination sustaining the levy. The taxpayer petitioned the U.S. Tax Court to contest this determination.

What is a CDP Hearing Supposed to Do?

The Collection Due Process hearing was added to the tax code in 1998 to give taxpayers a meaningful chance to be heard before the IRS levies on a bank accounts or garnishes wages. Section 6330 says that before the IRS can levy on property, it has to give the taxpayer written notice and the right to a hearing before the IRS Independent Office of Appeals.

The hearing is informal. There is no court reporter. There is no judge. It is a phone call or correspondence with a settlement officer in Appeals. But it matters, because what happens in that hearing dictates what happens later in U.S. Tax Court.

At the hearing, the taxpayer can raise “any relevant issue relating to the unpaid tax or the proposed collection action.” That includes spousal defenses, the existence or amount of the underlying tax liability, and challenges to the proposed collection action itself. The taxpayer can also propose a collection alternative — an installment agreement, currently not collectible, or an offer in compromise.

This is a powerful set of rights. But the rights only matter if the taxpayer actually uses them.

Can You Challenge the Underlying Tax in a CDP Case?

Sometimes. Section 6330(c)(2)(B) allows the taxpayer to challenge the existence or amount of the underlying liability only if the taxpayer “did not receive a statutory notice of deficiency for such tax liability or did not otherwise have an opportunity to dispute such tax liability.”

In the present case the taxpayer had filed his own returns showing the amounts owed. There were no Notices of Deficiency to ignore, because the IRS just assessed what the taxpayer reported. So in theory, the CDP hearing was his first chance to dispute the assessed liabilities. In theory.

The catch is that the U.S. Tax Court will only review the underlying liability if the taxpayer “properly raised” it during the CDP hearing. That standard comes from Giamelli v. Commissioner, 129 T.C. 107 (2007), and the regulations at Treas. Reg. § 301.6330-1(f)(2). Just showing up and saying “I disagree with the tax” is not enough. The taxpayer has to put something on the table–an amended return, evidence of incorrect income, anything that gives the settlement officer something to evaluate.

The taxpayer here did not do that. He kept circling back to the 2013 refund argument, which had nothing to do with 2015 through 2018 and had already been rejected twice on appeal. He never produced an amended return. He never identified an item of income or a deduction that he thought was wrong. So the U.S. Tax Court concluded he had not properly raised the underlying liability, and the court refused to review it.

There is a footnote in the opinion worth noting. The court said that even if the taxpayer had properly raised the issue, the outcome would not have changed because there was no evidence that the amounts on his self-filed returns were wrong. That is the practical reality. A taxpayer who files a return reporting a balance due is fighting uphill to later say the return was wrong.

What About a Collection Alternative?

The other reason to request a CDP hearing is to negotiate something other than a levy. Settlement officers consider installment agreements, offers in compromise, and currently not collectible status. To evaluate any of these, the settlement officer needs financial information. That is what Form 433-A is for. It is a collection information statement showing income, expenses, assets, and debts.

If the taxpayer does not provide a Form 433-A, the settlement officer cannot evaluate a collection alternative. There is nothing to evaluate. The Tax Court has held in case after case that an Appeals officer does not abuse his or her discretion by sustaining a levy when the taxpayer fails to submit required financial information.

That was the heart of the holding here. The settlement officer asked for the Form 433-A and the supporting documents three different times across two settlement officers. The taxpayer never sent anything. The Tax Court said sustaining the levy under those circumstances was not arbitrary or capricious. It was the only thing the settlement officer could do.

The Takeaway

The lesson from this case is that a CDP hearing is a one-shot opportunity–technically two, as taxpayers can request a hearing on the first lien and also on the first levy. You request it on Form 12153, and from that point forward, the settlement officer is the most important person in your case. If you want to challenge the underlying tax, you have to put real evidence on the table during the hearing–not after, and not in U.S. Tax Court. If you want a collection alternative, you have to provide a complete Form 433-A and the supporting documents the settlement officer asks for. Requesting delays, refusing to engage, and pointing to unrelated cases on appeal will not preserve any of your rights. It will close the door on them. Treat the CDP hearing as the case itself, because by the time you get to U.S. Tax Court, that is exactly what it was.

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 are Custom Settings in Salesforce?

Custom settings are objects that developers use to create different customized sets of data that have an association with the company, user, or profile. There are options where you can set the custom settings to either public or private. Some of the areas where custom settings get applied are the fields, Apex, flows, SOAP API, and validation rules. The data created by customer meetings must meet the user’s needs, allowing users to access it faster using the application cache. 

When you have data using the settings, users do not need to use database querying languages or the Salesforce Object Query Language to get the data. It uses custom objects which developers build to fix all the business processes and information that does not work well with the Salesforce objects. Many businesses should learn how to use custom settings and benefit from them. Some of the custom fields that the developers use are currency, checkbox, phone number, date and time, URL, text, number, textarea, percent, e.t.c.

The settings can lack some fields like lookups, formulas, picklists, e.t.c. which are important to use. It also lacks page layouts that developers can use. The lack of layouts forces developers to use visual force pages to meet the requirements. When working with these settings, there are no rules that one must use. 

                  Wish to make a career in the world of salesforce? Start with HKR’S  salesforce online training 

Types of Salesforce Custom Settings

We have two types of custom settings. This are:

List Custom Settings

It works with how the custom objects function. The main purpose of this custom setting is to cache all the data. It reduces the cost of the data due to easy access to the data. It makes the accessing of static data across the company easy. It eliminates the use of SOQL queries which are sometimes against the limits. What the users need to do is put the data in this type of setting without writing any SOQL for accessing the data. The data provided in the list settings does not vary according to the users or profiles, making it impossible for anyone in the company to access it.

The data is useful to different departments of the company. It enables the developers to have reusable data which everyone can access in the company. This setting is good for the type of data sets that companies use mostly in their salesforce applications.

We create a list custom settings by following the steps below:

  • Locate the menu and search for the Schema settings, toggle the button of Manage list custom settings to turn it on. By default, most of the settings are in hierarchy custom.
  • Under the Custom Setting Definition, input the names under the label and Object Name and then change the Setting type from Hierarchy to List.       List Custom Settings   
  • When working with data like phone numbers, when you input the country codes into the labels, It automatically fetches into the form without querying the database. After filling in the details under the label and other fields, click on the Save button.
  • Navigate to the custom fields, click on the New button, and it will open a new page where you get prompted to choose the Data type and choose the type according to the data you entered in the custom definition. If it was phone numbers, choose the phone and click Next. We will select text. 

List Custom 

  • On this page, there are several fields like Field label, length, field name, Description, e.t.c. Fill them out and click Save.
  • Under the created label, click on the Manage option to provide new fields.

created label

  • After all, the new fields click Save, and you can view your complete list of custom settings.

Salesforce Training

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

Hierarchy Custom Settings

Hierarchy custom settings help in ensuring the majority have the advantages for users. Its logic is efficient and enables users to customize their settings using different settings and rows. The settings match particular profiles and contacts that will meet the requirements of the company’s clients. This type of setting can scan all the client companies and their necessary profiles, look at the tasks handled by different people, and ensure that the final values shown to the user are more accurate and specific to what they want. 

It makes the companies make certain settings to several profile settings meant for the users, which get subjected to the user settings individually. They help the companies and their clients to define all their data hierarchically. This type of setting is suitable when defining defaults used by specific Salesforce applications, relying on the users, companies’ needs, and certain profiles. Hierarchy custom settings sync well with the Salesforce functionalities since they are highly customizable, and you can change them to meet the customer’s needs.

We can create an example of a Hierarchy Custom Setting using the steps below:

  • Navigate to the Custom Settings option, input the data under the Label, Object Name, Setting Type by default is a hierarchy and click on the Save button.
  • A new dialog box will open, and you will get prompted to choose the type of data type, select the one that matches your inputs, and Save.
  • Under the next step, fill in your Field Label, Length, Field Name, and Description, among others, and click on the Save option.

Hierarchy Custom Settings    

  • When the dialog opens, click on the New button to create organizational access to the data.
  • After saving, you will get options to add other alternatives.
  • Another dialog box will pop up, prompting the administrator to add the profiles that will get associated with the values. When you click the Save button, several users will be under the custom settings. And that’s the whole process of creating the hierarchy of custom settings.
How to Create Custom Settings

Log in to your Salesforce CRM, locate the Custom Settings, and several fields require one to fill. Under the label and Object name, input worker for both fields. Under the Settings section, choose between list and Hierarchy. Under Visibility, set it to public, enter the Description, then click on the Save button.

How to create custom settings

In some cases, you find that some parts of the settings section got disabled, you need to navigate to the schema settings and change the settings to enable it. Go to the custom fields and create the field by entering data into Field Label, Data type, API name, and action. To add data, hover over the Action settings to add more data.

Enroll in our Siebel CRM Admin Training program today and elevate your skills!

HKR Trainings Logo

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

Why do we need Custom Settings?

Using custom settings in the Salesforce CRM and applications has several benefits. This include :

  • It allows faster fetching of data, for example, if you have many records and you want to retrieve one row, you will use custom settings to get the result in a short period due to the ability of customer settings to get stored in the cache.
  • They also avoid the chances of hitting the governing limits. There are several governing limits from SQL queries, DML statements, Sendmail methods, SOSL queries, e.t.c.
  • Due to the use of application cache, one can have faster data access, leading to better performance.
  • It enables the users to access different data according to the user’s profile and role in the organization, which promotes data integrity.
  • If you lack knowledge about databases or the Salesforce Object Query Language, it helps you avoid learning them.

                  Wish to make a career in the world of salesforce? Start with HKR’S  salesforce online training  in Canada 

How to Fetch Custom Settings in Salesforce?

There are several ways of fetching custom settings in Salesforce. These methods are:

To fetch custom settings, it depends on the type of custom settings. Let us look at all types of settings.

How to fetch data on list custom settings.

We use the getAll() method to fetch certain custom fields found in List settings. The method returns a list of the names and all the setting records i.e 

Map var =

CustomApiName.getAll();

Eg: Map worker = Worker__c.getAll();

We use the getValues() method  to fetch the values that match with a certain dataset. It normally works for both the custom settings i.e 

CustomApiName var = CustomApiName.getValues(name of dataset);

For example Worker__c stud = Worker__c.getValues('Mark');

To fetch values for hierarchy custom settings, we use the methods below to achieve the same:

We use getOrgDefaults() method to return the data set records for the company i.e 

CustomApiName var = CustomApiName.getOrgDefaults();

We use getInstance(input the user id or the profile id) method to get data records for a certain user or profile details i.e

CustomApiName var = CustomApiName.getInstance(userId/ProfileId);

We use the getInstance() method to get the records for the logged users.

CustomApiName var = CustomApiName.getInstance();

Limitations of Custom Settings in Salesforce?

Some of the limitations of using Salesforce include:

  • Each custom setting can only handle 300 fields. If there are more than 300, they can’t support more than 300 fields.
  • When storing the cached data, the storage will depend on the licenses. For 1 MB, you get the multiplication by using the licenses each organization owns. For example, a company can support up to 4MB of storage if it uses four licenses.
  • When you want to access an undeleted custom setting, you will get an error if you don’t have permission to access the custom settings. 
  • There is no option to share the custom setting records and objects.
  • When creating the custom setting, you cannot get the ownership after its creation.
  • When dealing with each certified package, one gets a separate limit when working with the company limit.

Click here to get frequently asked Salesforce Interview Questions & Answers

Salesforce Training

Weekday / Weekend Batches

 Conclusion
When creating custom settings in a distributed package, you must develop several builds for populating the custom settings with data after the package installation. Implementing custom settings is easier and straightforward and has many benefits for the users. The article has enabled you to better understand the two types of custom settings, the advantages, and how to install them in your application.

Related articles:



Source link