IRS Collection Statute Expiration Date (CSED)

 I consider it odd.

I have two files in my office waiting on the collection statute of limitations to expire.

It is not a situation I often see.

Audits, penalty abatements, payment plans, offers and innocent spouse requests are more common.

Let’s talk about the running of the collection statute of limitations.

COMMENT: I do not consider this to be valid tax planning, and I am quite reluctant to represent someone who starts out by intending to do the run. That said, sometimes unfortunate things happen. We will discuss the topic in the spirit of the latter.

Let’s set up the two statutes of limitations:

(1) The first is the statute on assessment. This is the familiar 3-year rule: the IRS has 3 years to audit and the taxpayer has 3 years to amend.

COMMENT: I do not want to include the word “generally” every time, as it will get old. Please consider the modifier “generally” as unspoken but intended.

(2)  The second is the statute on collections. This period is 10 years.

We might conversationally say that the period can therefore go 13 years. That would be technically incorrect, as there would be two periods running concurrently. Let’s consider the following example:

·      You filed your individual tax return on April 15, 2020. You owed $1,000 above and beyond your withholdings and estimates.

·      The IRS audited you on September 20, 2022. You owed another $4,000.

·      You have two periods going:

o  The $1,000 ends on April 15, 2030 (2020 + 10 years).

o  The $4,000 ends on September 20, 2032 (2022 + 10 years).

Alright, so we have 10 years. The expiration of this period is referred to as the “Collection Statute Expiration Date” or “CSED”.

When does it start?

Generally (sorry) when you file the return. Say you extend and file the return on August 15. Does the period start on August 15?

No.

The period starts when the IRS records the return.

Huh?

It is possible that it might be the same date. It is more possible that it will be a few days after you filed. A key point is that the IRS date trumps your date.

How would you find this out?

Request a transcript from the IRS. Look for the following code and date:

                  Code          Explanation

                    150           Tax return filed

Start your 10 years.

BTW if you file your return before April 15, the period starts on April 15, not the date you filed. This is a special rule.

Can the 10 years be interrupted or extended?

Oh yes. Welcome to tax procedure.

The fancy 50-cent word is “toll,” as in “tolling” the statute. The 10-year period is suspended while certain things are going on. What is going on is that you are probably interacting with the IRS.

OBSERVATION: So, if you file your return and never interact with the IRS – I said interact, not ignore – the statute will (generally – remember!) run its 10 years.

How can you toll the statute?

Here are some common ways:

(1)  Ask for an installment payment plan

Do this and the statute is tolled while the IRS is considering your request.

(2)  Get turned down for an installment payment plan

                  Add 30 days to (1) (plus Appeals, if you go there).

(3)  Blow (that is, prematurely end) an installment payment plan

Add another 30 days to (1) (plus Appeals, if you go there).

(4)  Submit an offer in compromise

The statute is tolled while the IRS is considering your request, plus 30 days.

(5)  Military service in a combat zone

The statute is tolled while in the combat zone, plus 180 days.

(6)  File for bankruptcy

The statute is tolled from the date the petition is filed until the date of discharge, plus 6 months.

(7)  Request innocent spouse status

The statute is tolled from the date the petition is filed until the expiration of the 90-day letter to petition the Tax Court. If one does petition the Court, then the toll continues until the final Court decision, plus 60 days.

(8)  Request a Collections Due Process hearing

The statute is tolled from the date the petition is filed until the hearing date.

(9)  Request assistance from the Taxpayer Advocate

The statute is tolled while the case is being worked by the Taxpayer Advocate’s office.

Unfortunately, I have been leaning on CDP hearings quite a bit in recent years, meaning that I am also extending my client’s CSED. I have one in my office as I write this, for example. I have lost hope that standard IRS procedure will resolve the matter, not to mention that IRS systems are operating sub-optimally during COVID. I am waiting for the procedural trigger (the “Final Notice. Notice of Intent to Levy and Notice of Your Rights to a Hearing”) allowing the appeal. I am not concerned about the CSED for this client, so the toll is insignificant.

There are advanced rules, of course. An example would be overlapping tolling periods. We are not going there in this post.

Let’s take an example of a toll.

You file your return on April 15, 2015. You request a payment plan on September 5, 2015. The IRS grants it on October 10, 2015. Somethings goes wobbly and the IRS terminates the plan. You request a Collection Due Process hearing on June 18, 2019. The hearing is resolved on November 25, 2019.

Let’s assume the IRS posting date is April 15, 2015.

Ten years is April 15, 2025.

It took 36 days to approve the payment plan.

The plan termination automatically adds 30 days.

The CDP took 161 days.

What do you have?

April 15, 2025 … plus 36 days is May 21, 2025.

Plus 30 days is June 20, 2025.

Plus 161 days is November 28, 2025.

BTW there are situations where one might extend the CSED separate and apart from the toll. Again, we are not going there in this post.

Advice from a practitioner: do not cut this razor sharp, especially if there are a lot of procedural transactions on the transcript. Some tax practitioners will routinely add 4 or 5 weeks to their calculation, for example. I add 30 days simply for requesting an installment payment plan, even though the toll is not required by the Internal Revenue Manual.  I have seen the IRS swoop-in when there are 6 months or so of CSED remaining, but not when there are 30 days.

Pay Me In Bitcoin

 

He plays right guard for the Carolina Panthers and had a great quote about cryptocurrency:

         "Pay me in Bitcoin.”

We are talking about Russell Okung.

I believe he earned about $13 million for the 2020/2021 season, so he can move a lot of Bitcoin.

And Bitcoin had quite the run in 2020, moving from approximately $7,200 in January to $30,000 by year-end. The payment platform company Square added Bitcoin as an investment, and PayPal started a new service allowing its users to buy, hold and sell Bitcoin through their PayPal account.

Then there is, as always, the near inexplicable behavior of some people. In October, John McAfee (yes, John of McAfee computer security products) was arraigned for tax fraud. He was charged with, among other things, not reporting income for his work promoting cryptocurrencies.

The IRS is paying more attention.

We have existing guidance that the IRS views cryptos – which include Bitcoin and Ethereum – as property and not currency. While this might sound like an arcane topic for a business school seminar, it does have day-day-day consequences. If you buy something for $11 and pay with a $20 bill, there is likely no tax consequence.  A crypto is not currency, however. Pay for that $11 purchase using your Bitcoin and the IRS sees the trading of property.

What does that mean?

Taxwise you sold crypto for $11. You next have to determine your cost (that is, “basis”) in the crypto. If less than $11, you have a capital gain. If more than $11, you have a capital loss. The gain or loss could be long-term if you held the crypto for more than one year; otherwise, it would be a short-term gain or loss.

Assume that you have frequent transactions in crypto. How are you to determine your basis and holding period every time you pay with crypto?

You had better buy software to do this, or use a wallet that tracks it for you. Otherwise you could have a tax mess on your hands at the end of the year.

You can, by the way, also have ordinary taxable income (rather than capital gain) from cryptos. How? Say that you do consulting work for someone and they pay you in crypto.  You have gig income; gig income is ordinary income; that crypto is ordinary income to you.

By the way, mining Bitcoin is also ordinary income.

The IRS had a question about cryptos on a schedule in prior years, but for 2020 it is moving the following question to the top of Form 1040 page 1:

At any time during 2020, did you receive, sell, send, exchange, or otherwise acquire any financial interest in any virtual currency?”

The IRS moved the question to make it prominent, of course, but there is another reason. Remember that you are signing that tax return “to the best of your knowledge and belief” and “under penalties of perjury.” The IRS is raising the stakes for not reporting.

Expect more computer matching. Expect more notices.   

Even Treasury is upping its game.

There is a form that one files with the Treasury if one owns or has authority over $10,000 or more in a foreign bank or other financial account. We tax veterans remember it as the FBAR (Foreign Bank and Financial Accounts) report, but the name has since been revised to FinCen 114 (Financial Crimes Enforcement Network). Here is Treasury telling us that we will soon be reporting cryptos on their form:

Currently, the Report of Foreign Bank and Financial Accounts (FBAR) regulations do not define a foreign account holding virtual currency as a type of reportable account. (See 31 CFR 1010.350(c)).  For that reason, at this time, a foreign account holding virtual currency is not reportable on the FBAR (unless it is a reportable account under 31 C.F.R. 1010.350 because it holds reportable assets besides virtual currency).    However, FinCEN intends to propose to amend the regulations implementing the Bank Secrecy Act (BSA) regarding reports of foreign financial accounts (FBAR) to include virtual currency as a type of reportable account under 31 CFR 1010.350.

This area is moving in one direction – more reporting. There is currently some inconsistency in how cryptocurrency exchanges report to the IRS (Form 1099-B versus 1099-K versus 1099-MISC). I expect the IRS to lean harder – and soon - on standardizing this reporting. This genie is out of the bottle.

Happy New Year

 

State Taxation of Telecommuting

The year 2020 has brought us a new state tax issue.

To be fair, the issue is not totally new, but it has taken on importance with stay-at-home mandates.

Here is the issue: You work in one state but live in another. Which state gets to tax you when you are working from home?

Let’s start with the general rule: state taxation belongs to the state where the employee performs services, not the state where the employee resides. The concept is referred to as “sourcing,” and it is the same reason a state can tax you if you have rental real estate there.

Let’s follow that with the first exception: states can agree to not follow the general rule. Ohio, for example, has a reciprocal agreement with Kentucky. The agreement provides that an employee will be taxed by his/her state of residence, not by the state where the employee works.   A Kentucky resident working in Ohio, for example, will be taxed by Kentucky and not by Ohio.

Let’s pull away from the Cincinnati tristate area, however. That reciprocal agreement makes too much sense.

We need two other states: let’s use Iowa and Missouri.

One lives in Iowa and commutes to Missouri. Both states have an individual income tax. We have 2020, COVID and stay-at-home. An employee of a Missouri employer works from home, with home being Iowa.

Which state gets to tax?

This one is simple. Iowa.

Why?

Because both states have the same rule: the state of residence gets to tax a telecommuter.

So where is the issue in this area?

With states that are … less reasonable … than Iowa and Missouri.

Let’s go to Captain Obvious: New York.

New York has a “convenience of the employer” addendum to the above discussion. Under this rule, New York asks why the employee is working remotely: is it for the convenience of the employer, or is it for the convenience of the employee? The tax consequence varies depending on the answer.

* If for the convenience of the (New York) employer, then the employee’s state of residence has the first right to tax.

* If for the convenience of the (nonresident) employee, then New York has the first right to tax.

We for example have a Tennessee client with a New York employer who walked into this issue. He lives and works in Memphis, infrequently travelling to New York. We were able to resolve the matter, but New York initially went after him rather aggressively.

How does New York’s rule work with 2020 and COVID?

It doesn’t.

All those employees not commuting to New York were very much observing the convenience of their employer.

Clearly, this was an unacceptable answer to New York.

Let’s change the rule, said New York: the employee’s “assigned or primary” location will now control. If my accounting office was located in New York, for example, that would be my “assigned or primary” office and New York could tax me, no matter where I was.

How could I avoid that result? I would need to have my employer open a bona fide office where I lived. Some people could do that. Most could not.

Yessir.

There is no evolving tax doctrine here. This is ad hoc and reactive taxation, with much caprice, little constancy and the sense that New York will say and do whatever to lift your wallet.

There are few other states that follow this “convenience” rule: Pennsylvania, Delaware and New Jersey come to mind. It is more convenient for them to tax you than not to tax you, to reword the rule.

COVID introduced us to two more states feuding over the taxation of telecommuters: Massachusetts and New Hampshire. Massachusetts decreed that any employee who began working outside the state for “pandemic-related” circumstances would continue to be subject to Massachusetts income tax.

It is the same issue as New York, one might initially think. New Hampshire will allow a tax credit for the tax paid Massachusetts. The accounting fee goes up, but it works out in the end, right?

Nope.

Why?

New Hampshire does not tax W-2 income.

How do states like Massachusetts or New York justify their behavior?

There is an argument: Massachusetts and New York have roads, infrastructure, schools, universities, hospitals and so forth that attracted employers to locate there. Their tax is a fair and appropriate levy for providing and sustaining an environment which allows a person to be employed.

Got it.

Don’t buy it.

I grew up in Florida, which does not have an individual income tax. Somehow the state nonetheless has roads, infrastructure, schools, universities, hospitals and so forth. The only explanation must be divine intervention, it appears.

Additionally, if I lived in New Hampshire – and worked from there – I might prefer that my taxes go to New Hampshire. I after all would be using its roads, infrastructure, schools, universities, hospitals and so on, putting little – or no – demand on Massachusetts. I might in fact be quite pleased to not commute into Massachusetts regularly, if it all. It seems grotesque that Massachusetts will chase me across the fruited plains just because I need a job.

New Hampshire has filed a complaint against Massachusetts with the Supreme Court. The argument is rather simple: Massachusetts is infringing by imposing its tax on New Hampshire residents working in New Hampshire.  Interestingly, Connecticut and New Jersey have filed amicus (“friend of the court”) briefs supporting New Hampshire’s position. Their beef is with New York and not Massachusetts, but they are clearly interested in the issue.

I personally expect the expansion and growing acceptance of telecommuting to be a permanent employment change as we come out of COVID and its attendant restrictions. With that as context, the treatment of telecommuting may well be one of the “next big things” in taxation.

Deducting “Tax Insurance” Premiums

 There is an insurance type that I have never worked with professionally: tax liability insurance.

It is what it sounds like: you are purchasing an insurance policy for unwanted tax liabilities.

It makes sense in the area of Fortune 500 mergers and acquisitions. Those deals are enormous, involving earth-shaking money and a potentially disastrous tax riptide if something goes awry. What if one the parties is undergoing a substantial and potentially expensive tax examination? What if the IRS refuses to provide advance guidance on the transaction? There is a key feature to this type of insurance: one is generally insuring a specific transaction or limited number of transactions. It is less common to insure an entire tax return.  

My practice, on the other hand, has involved entrepreneurial wealth – not institutional money - for almost my entire career. On occasion we have seen an entrepreneur take his/her company public, but that has been the exception. Tax liability insurance is not a common arrow in my quiver. For my clients, representation and warranty insurance can be sufficient for any mergers and acquisitions, especially if combined with an escrow.

Treasury has been concerned about these tax liability policies, and at one time thought of requiring their mandatory disclosure as “reportable” transactions. Treasury was understandably concerned about their use with tax shelter activities. The problem is that many routine and legitimate business transactions are also insured, and requiring mandatory disclosure could have a chilling effect on the pricing of the policies, if not their very existence. For those reasons Treasury never imposed mandatory disclosure.

I am looking at an IRS Chief Counsel Memorandum involving tax liability insurance.

What is a Memorandum?

Think of them as legal position papers for internal IRS use. They explain high-level IRS thinking on selected issues.

The IRS was looking at the deductibility by a partnership of tax insurance premiums. The partnership was insuring a charitable contribution.

I immediately considered this odd. Who insures a charitable contribution?

Except …

We have talked about a type of contribution that has gathered recent IRS attention: the conservation easement.

The conservation easement started-off with good intentions. Think of someone owning land on the outskirts of an ever-expanding city. Perhaps that person would like to see that land preserved – for their grandkids, great-grandkids and so on – and not bulldozed, paved and developed for the next interchangeable strip of gourmet hamburger or burrito restaurants. That person might donate development rights to a charitable organization which will outlive him and never permit such development. That right is referred to as an easement, and the transfer of the easement (if properly structured) generates a charitable tax deduction.

There are folks out there who have taken this idea and stretched it beyond recognition. Someone buys land in Tennessee for $10 million, donates a development and scenic easement and deducts $40 million as a charitable deduction. Promoters then ratcheted this strategy by forming partnerships, having the partners contribute $10 million to purchase land, and then allocating $40 million among them as a charitable deduction. The partners probably never even saw the land. Their sole interest was getting a four-for-one tax deduction.

The IRS considers many of these deals to be tax shelters.

I agree with the IRS.

Back to the Memorandum.

The IRS began its analysis with Section 162, which is the Code section for the vast majority of business deductions on a tax return. Section 162 allows a deduction for ordinary and necessary expenses directly connected with or pertaining to a taxpayer’s trade or business.

Lots of buzz words in there to trip one up.

You my recall that a partnership does not pay federal tax. Instead, its numbers are chopped up and allocated to the partners who pay tax on their personal returns.

To a tax nerd, that beggars the question of whether the Section 162 buzz words apply at the partnership level (as it does not pay federal tax) or the partner level (who do pay federal tax).

There is a tax case on this point (Brannen). The test is at the partnership level.

The IRS reasoned:

·      The tax insurance premiums must be related to the trade or business, tested at the partnership level.

·      The insurance reimburses for federal income tax.

·      Federal income tax itself is not deductible.

·      Deducting a premium for insurance on something which itself is not deductible does not make sense.

There was also an alternate (but related argument) which we will not go into here.

I follow the reasoning, but I am unpersuaded by it.

·      I see a partnership transaction: a contribution.

·      The partnership purchased a policy for possible consequences from that transaction.

·      That – to me - is the tie-in to the partnership’s trade or business.

·      The premium would be deductible under Section 162.

I would continue the reasoning further.

·      What if the partnership collected on the policy? Would the insurance proceeds be taxable or nontaxable?

o  I would say that if the premiums were deductible on the way out then the proceeds would be taxable on the way in.

o  The effect – if one collected – would be income far in excess of the deductible premium. There would be no further offset, as the federal tax paid with the insurance proceeds is not deductible.

o  Considering that premiums normally run 10 to 20 cents-on-the-dollar for this insurance, I anticipate that the net tax effect of actually collecting on a policy would have a discouraging impact on purchasing a policy in the first place.

The IRS however went in a different direction.

Which is why I am thinking that – albeit uncommented on in the Memorandum – the IRS was reviewing a conservation easement that had reached too far. The IRS was hammering because it has lost patience with these transactions.

Merry Christmas

 

Inheriting A Tax Debt

 I am looking at a decision coming from a New Jersey District Court, and it has to do with personal liability for estate taxes.

Clearly this is an unwanted result. How did it happen?

To set up the story, we are looking at two estates.

The first estate was the Estate of Lorraine Kelly. She died on December 30, 2003. The executors, one of whom was her brother, filed an estate tax return in September, 2004. The estate was worth over $1.7 and owed $214 grand in tax. Her brother was the sole beneficiary.

OK.

The estate got audited. The estate was adjusted to $2.6 million and the tax increased to $662 grand.

COMMENT: It does not necessarily mean anything that an estate was adjusted. Sometimes there are things in an estate that are flat-out hard to value or – more likely – can have a range of values. I will give you an example: what is the likeness of Prince (the musician) worth? Reasonable people can disagree on that number all day long.

The estate owed the IRS an additional $448 grand.

The brother negotiated a payment plan. He made payments to the IRS, but he also transferred estate assets to himself and his daughter, using the money to capitalize a business and acquire properties. He continued doing so until no estate assets were left. The estate however still owed the IRS.

OK, this is not fatal. He had to keep making those payments, though. He might want to google “transferee tax liability” before getting too froggy with the IRS.

He instructed his daughter to continue those payments in case something happened to him. There must have been some forewarning, as he in fact passed away.

His estate was worth over a million dollars. It went to his daughter.

The daughter he talked to about continuing the payments to the IRS.

Guess what she did.

Yep, she stopped making payments to the IRS.

She had run out of money. Where did the money go?

Who knows.

COMMENT: Folks, often tax law is not some abstruse, near-impenetrable fog of tax spew and doctrine descending from Mount Olympus. Sometimes it is about stupid stuff – or stupid behavior.

Now there was some technical stuff in this case, as years had passed and the IRS only has so much time to collect. That said, there are taxpayer actions that add to the time the IRS has to collect. That time is referred to as the statute of limitations, and there are two limitations periods, not one:

·      The IRS generally has three years to look at and adjust a tax return.

·      An adjustment is referred to as an assessment, and the IRS then has 10 years from the date of assessment to collect.

You can see that the collection period can get to 13 years in fairly routine situations.

What is an example of taxpayer behavior that can add time to the period?

Let’s say that you receive a tax due notice for an amount sufficient to pay-off the SEC states’ share of the national debt. You request a Collections hearing. The time required for that hearing will extend the time the IRS has to collect. It is fair, as the IRS is not supposed to hound you while you wait for that hearing.

Back to our story.

Mrs. Kelley died and bequeathed to her brother.

Her brother later died and bequeathed to his daughter

Does that tax liability follow all the way to the daughter?

There is a case out there called U.S. v Tyler, and it has to do with fiduciary liability. A fiduciary is a party acting on behalf of another, putting that other person’s interests ahead of their own interests. An executor is a party acting on behalf of a deceased. An executor’s liability therefore is a fiduciary liability. Tyler says that liability will follow the fiduciary like a bad case of athlete’s foot if:

(1)  The fiduciary distributed assets of the estate;

(2)  The distribution resulted in an insolvent estate; and

(3)  The distribution took place AFTER the fiduciary had actual or constructive knowledge of the unpaid taxes.

There is no question that the brother met the Tyler standard, as he was a co-executor for his sister’s estate and negotiated the payment plan with the IRS.

What about his daughter, though?

More specifically, that third test.

Did the daughter know – and can it be proven that she knew?

Here’s how: she filed an inheritance tax return showing the IRS debt as a liability against her father’s estate.

She knew.

She owed.

Our case this time was U.S. v Estate of Kelley, 126 AFTR 2d 2020-6605, 10/22/2020.