A Ponzi Scheme And Filing Late

I am reading a case involving a late tax return, a Ponzi scheme, and an IRS push for penalties.

It made me think of this form:

It is used for one of two reasons:

(1)  Someone is filing a tax return with numbers different from a Schedule K-1 received from a passthrough entity (such as a partnership).

(2)  Someone is amending a TEFRA partnership return.

That second one is a discussion for another day. Let’s focus instead on the first reason. How could it happen?

Easy. You are a partner in a partnership. You bring me your Schedule K-1 to prepare your personal return. I spot something wrong with the K-1, and the numbers are large enough to matter. We contact that partnership to amend the return and/or your K-1. The partnership refuses.

COMMENT: We would use Form 8082 to inform the IRS that we are not using numbers provided on your K-1.

This is a tough spot to be in. File the form and you are possibly waiving a flag at the IRS. Fail to file it and the IRS has procedural rights, and those include the right to change your numbers back to the original (and disputed) K-1.

There is another situation where you may want to file Form 8082.

Let’s look at the Rosselli case.

Mr. Roselli (Mr. R) was a housing appraiser. Mrs. Rosselli was primarily a homemaker. Together they have five children, three of whom have special needs.

Through his business, Mr. R came to know the founder of a solar energy company (DC Solar). Turns out that DC Solar was looking for additional capital, and Mr. R knew someone looking to invest. The two were introduced and – in gratitude – Mr R became a managing member in DC Solar via his company Halo Management Services LLC.

This part turned out well for the R’s. In 2017 DC Solar paid Halo approximately $300 grand. In 2018 DC Solar paid approximately $414 grand. Considering they had no money invested, this was all gravy for the R's.

COMMENT: Notice that Halo was paid for management services. Halo in turn was Mr. R, so Mr. R got paid over $700 grand over two years for services performed. This was a business, and Mr. R needed to report it on his tax return like any other business.

In late 2018 the FBI raided DC Solar’s offices investigating whether the company was a Ponzi scheme. The owners of DC Solar were eventually indicted and pled guilty, so I guess the company was.

Let’s roll into the next year. It was tax time (April 15, 2019) and there was not a K-1 from DC Solar in sight.

COMMENT: You think?

The accountant filed an extension until October 15. It did not matter, as the R’s did not file a tax return by then either.

The IRS ran a routine check on DC Solar and its partners. It did not take much for the IRS to flag that the R’s had not filed a 2018 return. The IRS contacted the R’s, who contacted their accountant, eventually filing their 2018 return in January 2022.

You know what was on that 2018 return? The $414 grand in management fees.

You know what was not on that 2018 return? A big loss from DC Solar.

Here is Mr. R:

Mr. Carpoff informed me that I was to receive Schedule K-1s showing large ordinary losses for 2018 from DC Solar, and as a result I would not have a tax liability for that year. However, before the K-1s could be issued … DC Solar’s offices were raided by the FBI.”

All of DC Solar’s documents and records were seized by federal authorities in the ensuing investigation. As a result, I was unable to determine any tax implications because I did not receive a K-1 or any other tax reporting information from DC Solar.”

Got it: Mr. R was expecting a big loss to go with that $414 grand. And why not? DC Solar had reported a big loss to him for 2017, the prior year.

But the IRS Collections machinery had started turning. By August 2022, the IRS was moving to levy, and the R’s filed for a Collection Due Process (CDP) hearing.

COMMENT: There is maddening procedure about arguing underlying tax liability in a CDP hearing, which details we will skip. Suffice to say, a taxpayer generally wants to fight any proposed tax liability like the third monkey boarding Noah’s ark BEFORE requesting a CDP hearing.

At the conclusion of the CDP hearing, the IRS decided that they had performed all the required procedural steps to collect the R’s 2018 tax. The R’s disagreed and filed with the Tax Court.

The R’s presented three arguments.

• They reasonably assumed that they would not be required to file or pay tax for 2018 because of an expected loss from the DC Solar K-1.

The Court was not buying this. Not owing any taxes is not the same as not being required to file. This was not a case where someone did not work, meaning they dd not have enough income to trigger a filing requirement. The Rs instead had a more complicated return, with income here and deductions or losses there. Granted, it might compress to no tax due, but they needed to file so one could follow how they got to that answer.

• The R’s reasonably relied on advice from their accountant and others.

The Court did not buy this either. For one thing, the Rs had never informed their accountant about the $414 grand in management fees. If one wants to rely on a professional’s advice, one must provide all available pertinent information to the professional. The Court was not amused that the R’s had not shared the LARGEST number on their return with their accountant.

• The R’s argued that they would experience “undue hardship” from paying the tax on its due date.

The R’s argued that their income died up when DC Solar was raided. Beyond that, though, they had not provided further information on what “drying up” meant. Without information about their assets, liabilities and remaining sources of income, the Court found the R’s argument to be self-serving.

Also, the Court did not ask – but I will – what the R's had done with the $700 grand in management fees they received in 2017 and 2018.

Yeah, no. The Court found for the IRS, penalties and all.

And here is what I am thinking:

What if they had timely filed their 2018 return, showing a loss from DC Solar equal to the management fees?

Problem: there was no K-1 from DC Solar.

Answer: attach the 8082.

I think the tax would eventually have turned out the same.

But I also think they would have had a persuasive case for abatement of penalties for late filing and late payment. The penalty for late file and pay is easily 25%, so that abatement is meaningful.

Our case this time was Rosselli v Commissioner, TC Bench Opinion, October 23, 2023.

Waiting Too Long For Refund Of Excess Withholdings

It happens when someone fails to file with the IRS. It might be a “sleeping dog” rationalization, but people will allow a string of tax years to go unfiled, even if some of those years have refunds rather than tax due.

This is a trap, and I saw it sprung earlier this year on a widow. It was unfortunate, as she still has kids at home and could use the money.

The trap is that tax refunds are not payable after a period of time. The Code wants closure on tax matters. The IRS has three years to audit you. You in turn have three years to request a refund. These are general rules, and there are relief valves for the unusual situation: the IRS can request you to voluntarily extend the statute, for example, or you can file a protective claim if your three years are running out.

Let’s look at the Golden case.

Michael Golden did not file his 2015 tax return. In fact, he waited so long that the IRS prepared a return for him (called a substitute for return or SFR). The IRS does not spot a taxpayer any breaks when they do this (no itemized deductions or head of household status, for example). The IRS instead is trying to get a taxpayer’s attention, prompting them to file a return and opt back into the system. In April 2021 (five years after the return was actually due) the IRS issued its notice of deficiency (NOD, sometimes referred to as SNOD). The SNOD is the IRS trying to perfect its assessment prior to sending the account to Collections for their tender mercies. The SNOD showed tax due.

A few days after receiving the SNOD, Golden filed his 2015 tax return. It showed a refund.

Of course.

Golden wanted his refund. The IRS said it could not issue a refund.

There is a technical rule.  

Here it is:

         Section 6511(a)  Period of limitation on filing claim.

Claim for credit or refund of an overpayment of any tax imposed by this title in respect of which tax the taxpayer is required to file a return shall be filed by the taxpayer within 3 years from the time the return was filed or 2 years from the time the tax was paid, whichever of such periods expires the later, or if no return was filed by the taxpayer, within 2 years from the time the tax was paid. Claim for credit or refund of an overpayment of any tax imposed by this title which is required to be paid by means of a stamp shall be filed by the taxpayer within 3 years from the time the tax was paid.

Tax law can be tricky, but there are two rules here:

(1) The default period is three years (to coincide with the statute of limitations). The period starts on April 15 (when the return is due) and ends 3 years later, unless one requested an extension, in which case the default period also includes the extension (normally to October 15).

(2) Refuse to go along with the default rule and you might trigger the second rule: only taxes paid within two years of filing can be refunded.

As a generalization, you do not want the second rule. Why limit yourself to taxes paid within two years when you can have taxes paid within three years (and the extension period, if an extension was requested).

The IRS was also looking at this shiny:

Section 6511(b) Limitation on allowance of credits and refunds.

(1)  Filing of claim within prescribed period.

No credit or refund shall be allowed or made after the expiration of the period of limitation prescribed in subsection (a) for the filing of a claim for credit or refund, unless a claim for credit or refund is filed by the taxpayer within such period.

Notice that Congress included the phrase “shall be allowed.” Another way to say this is that – if you do not fit within the three-year test or the two-year test – your refund claim “shall” not be allowed. This was the IRS position: hey, we do not have much discretion here.

Let’s review the dates for Golden.

We are talking about his 2015 return. The return was due April 15, 2016. Add three years. Let’s be kind and add three years plus the extension. His three years clock-out on October 15, 2019. Three years will not get you to a refund.

The two year rule is even worse.

Golden argued fairness. He was working in the private sector as well as the Navy Reserve, and the demands therefrom made his life “extremely difficult.” In tax terms, this argument is referred to as “equity.” Some courts can consider equitable arguments, but the Tax Court is not one of them.

Here is the Court:

          We sympathize with petitioner’s predicament.

The Supreme Court has made clear that the limitations on refunds of overpayments prescribed in section 6512(b)(3) shall be given effect, consistent with Congress’s intent as expressed in the plain text of the statute, regardless of any perceived harshness to the taxpayer. See Commissioner v. Lundy, 516 U.S. at 250–53. Because Congress has not given us authority to award refunds based solely on equitable factors, we are compelled to grant respondent’s Motion for Summary Judgment.”

It was not a total loss for Golden, however. Since he did file a return, the IRS reduced his 2015 tax due to zero. He did not owe anything. He could not, however, recover any overpayment. He left that 2015 refund on the table.

What do you do if you are caught in a work situation like Golden? It is not a perfect answer, but file with the information you can readily assemble. Pay someone to prepare the return (within reason, of course). Hey, maybe you missed interest on a small money market account or took the standard deduction when itemized deductions would have given you a smidgeon more. The IRS will let you know about the first one (computer matching), and if there is enough money there you can amend later (the second one). At least you will get your basic refund claim in.

Our case this time was Golden v Commissioner, T.C. Memo 023-103.

Why You Always Use Certified-Mail For A Paper-Filed Return

Just about all tax returns are moving to electronic filing.

It makes sense. Our server sends a return to the government server, starting the automated processing of the return. Minimal manpower, highly automated, more efficient.

COMMENT: Electronic filing however does allow states and other filing authorities to include filing “bombs,” which can be very frustrating. We had a bomb recently with the District of Columbia. It could have been resolved – should have, in fact – but that would have required someone in D.C.  to answer our e-mail request or telephone call. Belatedly realizing this was a bar too high, we called the client to inform them of a change in plans. We would be paper filing instead.

Sometimes a state will say they never received a return. Our software maintains log events, such as electronic transmission of returns and their acceptance by the taxing authority. Tennessee has done this over the last few years as they updated some of their systems. Fortunately, the matter generally resolves when we present proof of electronic filing.

Do you remember when – not too many years ago – standard professional advice was to send tax returns using either certified or registered mail? That was that era’s equivalent of today’s electronic filing. We used to, back in the Stone Age, send our April 15^th individual extensions as follows:

·      Include multiple extensions per envelope. There could be several envelopes depending on the number of extensions.

·      Include a cover sheet detailing the extensions included in the envelope.

·      Certify the mailing of the envelope.

The problem with this procedure is that it could be abused. One could mail an empty envelope to the IRS, certifying the same. If any question came up, one could point to that envelope as “proof” of whatever. I do not know how often this happened in practice, but I recall having this very conversation with IRS representatives.

This reminds me of a recent case dealing with an issue arising from putting a paper-filed return in the mail. As we move exclusively to electronic filing, this issue will transition to history – along with rotary phones and rolodexes.

Let’s talk about the Pond case.

The IRS audited Stephen Pond’s return and made a mistake, concluding that Pond had underpaid his taxes. Pond paid the notice for tax due and interest on the 2012 tax year. The matter also affected 2013, so Pond overpaid his taxes for that year also. Pond’s accountant caught the mistake and filed for a refund for both years.

The accountant did the following:

(1)  He mailed the 2012 and 2013 tax refund claims in the same envelope to Holtsville, New York.

(2) He mailed a claim for refund of overpaid 2012 interest to Covington, Kentucky, which in turn forwarded the matter to Andover, Massachusetts.

Andover responded first. It wanted proof of the underlying 2012 filing (as the overpaid interest was for 2012). It took a while, but Pond eventually received his 2012 refund, including interest.

Time passed. There was no word about 2013. Pond contacted the IRS and was told the IRS never received the 2013 amended return.

COMMENT: While not said, I have a very good guess what happened. The IRS has had a penchant for stapling together whatever arrives in a single envelope. For years I have recommended separate envelopes for separate returns, as I was concerned about this possibility. It raised the cost of mailing, but I was trying to avoid the staple-everything-together scenario.

Pond sent a duplicate copy of his 2013 amended return.

Months went by. Crickets.

Pond contacted Holtsville and was informed that the IRS had closed the 2013 file.

Oh, oh.

A couple of weeks later Pond received the formal notice that the IRS was denying 2013 because it had been filed after statute of limitations had run.

Pond filed a formal protest. He filed with Appeals. He eventually brought suit in district court. The district court held against Pond, so he is now in Appeals Court.

This is tax arcana here that we will summarize.

     (1)  The general way to satisfy a statutory filing requirement is physical delivery.

(2)  Mail can constitute physical delivery.

a.    However, things can happen after one drops an envelope into the mailbox. The post office can lose it, for example. It would be unfair to hold someone responsible for a post office error, so physical delivery has a “mailbox” subrule:

If one can prove that an item was mailed, the subrule presumes that the item was timely delivered.

NOTE: Mind you, one still must prove that one timely put the item in the mail.

(3)  Congress codified the mailbox rule in 1954 via Section 7502. That section first included certified and registered mail as acceptable proof of filing, and the rule has been expanded over the years to include private delivery services and electronic filing.

(4) The question before the Court was whether Section 7502 supplanted prior common law (physical delivery, mailbox rule) or rather was supplementary to it.

a.    Believe it or not, the courts have split on this issue.

b.    What difference does it make? Let me give an example.      

There is an envelope bearing a postmark date of October 5, 20XX (that is, before the October 15^th extension deadline). The mail was not certified, registered, or delivered by an approved private delivery service.

If Section 7502 supplanted common law, then one could not point to that October 5 date as proof of timely filing. The only protected filings are certified or registered mail, private delivery service or electronic filing.

If Section 7502 supplemented but did not override common law, then that October 5 date would suffice as proof of timely mailing.

Let’s fast forward. The Appeals Court determined that Pond did not qualify under the safe harbors of Section 7502, as he did not use certified or registered mail. He could still prove his case under common law, however. Appeals remanded the case to the District Court, and Pond will have his opportunity to prove physical delivery.

My thoughts?

If you are paper filing – especially for a refund - always, always certify the mailing. Mind you, electronic filing is better, but let’s assume that electronic filing is not available for your unique filing situation. Pond did not do this and look at the nightmare he is going through.

Our case this time was Stephen K Pond v U.S., Docket No 22-1537, CA4, May 26, 2023.

 

Choose The Lesser Of IRS Grumpiness

 

Let’s talk about the failure to file (FTF) penalty.

Most of us must file an annual income tax return. Unless one is an expat (that is, an American living overseas), the return is due April 15. One can extend the return for six months (that is, until October 15), but the extension is for filing paperwork and not for payment of tax.

How is one supposed to estimate the tax if a significant amount of information is unavailable? Many times, there are estimates or informed guesses; the tax preparer will extend the return using those. Sometimes there are no estimates and no informed guesses; one then does their best. I doubt there isn’t a veteran tax preparer that hasn’t been blindsided by a Schedule K-1.

Let’s continue.

You extend your return. Your K-1 comes in heavier than expected. You owe $5,000 in tax with the return, which you file and pay on October 15.

You will have something called the Failure to Pay (FTP) penalty. The tax nerds know this as the Section 6651(a)(2) penalty. The penalty is as follows:

One-half of 1% for each month or part of a month

To a maximum of 25%

Let’s use our $5,000 example.

I count seven months from April through October (remember: a part of a month counts as a month).

The FTP penalty would be $5,000 times .005 times 7 = $175. It stings, but it is not crushing.

Let’s say the return was filed on October 30.

Has something changed?

Yep.

The IRS is strict about filing deadlines. If the return is extended to October 15, then you have until October 15 to file the return (or at least put it in the mail or submit the electronic file). The 15th is not a suggestion.

What happens if you miss the deadline?

You then filed your return late.

Back to our example. You file the return on October 30. You are just 15 days late. How bad can 15 days be?

It is not intuitive. If you file the return on October 30, you have blown the extension, meaning it is like you never submitted an extension at all. Any penalty calculation starts on April 16.

So what? The FTP penalty is still the same: $5,000 times .005 times 7, right?

The difference is that you have just provoked FTP’s big brother: the Failure to File (FTF) penalty. The FTF is the gym-visiting, MMA-training, creatine supplementing and aggressive sibling to the FTP.

Start with the FTP penalty. Multiply it by 10. The tax nerds know the FTF as the Section 6651(a)(1) penalty. 

Are we saying the FTF penalty is $5,000 times .05 times 7?

Nope, this is tax. There is a loop-the-loop to the FTF calculation.

• The maximum (a)(1) and (a)(2) penalty is 5% per month or part of a month.
• The math stops when you get to 25% in total.

The first loop means that the FTP penalty comes in at .005 and the FTF penalty comes in at .045 per month (or part thereof), as the maximum cannot exceed .050 per month.

The second loop means that the math stops when you get to 25%.

How does a tax pro handle this?

Easy: multiply by 25%.

Let’s go back to the math: $5,000 times 25% = $1,250.

This could have stopped at $175 had you just filed the return on October 15. Nah, you thought to yourself. What’s another couple of weeks?

$1,075, that’s what ($1,250 - $175). That is an expensive two weeks.

So, what got me fired up about this topic?

I saw the following on a tax return this past week:

Go to the bottom where it reads “Interest Penalties.” Go across to “Failure to File.” You will see $3,619.

Someone has just thrown away over three-and-a half grand by dragging their feet on filing. There goes a vacation, new electronics for the house, an IRA contribution - anything better than sending it to the government.

The client has two years of this, BTW.

But CTG, you say, maybe they did not have the money to pay.

The FTF does not mean that one is unable to pay. Granted, in real life the two issues often go together. One rationalizes. I do not have any money; if I delay filing maybe I can also delay IRS dunning letters and collection activity.

Maybe, but practice tells me it is rarely worth it. You have to go over four years with an FTP penalty before you equal just five months of FTF penalty. That money is just too expensive.

Let’s go back to our example.

Say the $5,000 is for tax year 2021. The taxpayer filed the return on or before October 15, 2022 and only now can pay the tax. What have we got?

First, the FTF penalty goes away, as the return was filed on time.

Second, the FTP penalty would be: $5,000 times .005 times 16 = $400. (I am running the penalty from April 2022 to July 2023)

Third, there will be interest, of course, but let’s ignore that for now.

$400 versus $1,075. Seems clear to me.

What can be done if one cannot get numbers together by October 15?

Here’s a thought.

I have a client who owns a successful drywalling company. We extended his return several years ago, and sure enough – closing in on October 15 – he was out-of-town, relaxed and unconcerned about any looming doom. However, I knew that he had a good year, and that any tax due was going to be significant. An FTF penalty on significant tax due was also going to be significant. We decided to file his return with the best numbers available, intending to amend whenever we obtained more precise numbers.

Did I like doing that?

That is a No.

Did he avoid the FTF?

That is a Yes, but he delayed getting us more accurate numbers. That delay created its own problems. Problems which were … completely … avoidable.

What is our takeaway?

File your return. Extend if you must, but file by the extension date. File even if you cannot pay. Yes, the IRS will penalize you. The IRS is grumpy about not getting its money. The IRS is grumpier, however, about not getting the tax return in the first place.

Remember: when given the option, choose the lesser of IRS grumpiness.

A Tax Refund When The IRS Fails To Process A Return

I am looking at a case involving a tax refund. The IRS bounced it, and I am having a hard time figuring out what the IRS was thinking.

Let’s talk about it.

James Willetts filed an extension for his 2014 individual tax return. He sent a $8,000 payment and extended the return from April 15 to October 15, 2015.

Standard stuff.

He did not file the return by October 15, 2015.

Oh well.

He finally filed the 2014 return on April 14, 2018.

April 15, 2015 to April 14, 2018 is less than three years, and that is not even including the six-month extension on the 2014 return.

The IRS rejected the return because of potential identity theft.

I presume that the IRS sent a notice, but Willetts did not respond. The Court goes on to observe that it was unclear whether Willetts even knew there was an identity issue before bringing suit.

COMMENT: That struck me as odd, as one of the first things a tax professional would do is obtain a transcript of Willett’s tax account. I then noted that Willetts brought suit as “pro se,” generally interpreted as going to Court without professional representation. Technically, that is incorrect, as one can go to Court with a CPA and still be considered “pro se,” but, in Willetts’ case, I am inclined to believe he was truly pro se.

The issue before the Court was straight-forward: did Willetts file his return in time to get his refund?

Let’s go tax nerd for a moment:

(1)  A taxpayer may recoup a tax overpayment by filing a claim within a statutorily-prescribed period of time.

(2)  That period of time is:

a.    Three years from when the return was filed, if the return was filed within three years of when the return was due; otherwise

b.    … two years from when the tax was paid.

(3)  The three years in (2)(a) extends with a valid tax extension.

Let’s parse this.

(1) Willetts' 2014 tax return was due April 15, 2015.

(2) He had a valid extension until October 15, 2015.

(3) His three-year period for filing a refund claim would run – at a minimum - until April 15, 2018. Since he also had a valid extension, the extension period gets tacked-on. He therefore had until October 15, 2018 to file a refund claim within the three-year lookback period.

You can see where the IRS was coming from. It did not have a tax return in its system until after October 15, 2018.

However, Willetts filed - or at least attempted to file - a return on April 14, 2018. It wasn’t his fault that the IRS held up processing.

The Court made short work of this.

A tax return is deemed filed the day it is received by the IRS, regardless of whether it is accepted, processed, ignored or destroyed by the IRS. The IRS’ own records showed Willetts' return as received on May 2, 2018, well within the period ending October 15, 2018.

The return was filed timely. Willetts was due his refund.

I have a couple of observations:

(1)  I do not understand why the IRS pursued this. The rules here are bright-line. The IRS did not have a chance of winning; in fact, the case strikes me as borderline harassment. 

What concerns me is the mountain of paper returns – especially amended returns – waiting unopened and unprocessed at the IRS as I write this. Are we going to see Willetts-like foot-dragging by the IRS on those returns? Is the IRS going to force me to file with the Tax Court to get my clients their refunds?   

(2)  Let’s play what-if.  

Say that Willetts had filed his return on November 1, 2018, so that all parties would agree that he was outside the three-year lookback period. Once that happened, his refund would be limited to any taxes paid within the previous two years. His 2014 taxes would have been deemed paid on April 15, 2015, meaning that none, zero, zip of his 2014 taxes were paid within two years of November 1, 2018. There would be no refund. This, by the way, is the how-and-why people lose their tax refunds if they do not file their returns within three years.   

Our case this time was Willetts v Commissioner, Tax Court November 22, 2021.

Penalties, Boyle and “Reductio Ad Absurdum.”

 

In logic there is an argument referred to as “reductio ad absurdum.” Its classic presentation is to pursue an assertion or position until it – despite one progressing logically – results in an absurd conclusion. An example would be the argument that the more sleep one gets, the healthier one is. It does not take long to get to the conclusion that someone who sleeps 24 hours a day – in a coma, perhaps – is in peak physical condition.

I am looking at a tax case that fits this description.

What sets it up is our old nemesis – the Boyle decision. Boyle hired an attorney to take care of an estate tax return. The attorney unfortunately filed the return a few months late, and the IRS came with penalties a-flying. Boyle requested penalty abatement for reasonable cause. The Court asked for the grounds constituting reasonable cause. Boyle responded:

                  I hired an ATTORNEY.”

Personally, I agree with Boyle.

The Court however did not. The Court subdivided tax practice in a Camusian manner by holding that:

·      Tax advice can constitute reasonable cause, as the advice can be wrong;

·      Relying on someone to file an extension or return for you cannot constitute reasonable cause, as even a monkey or U.S. Representative could google and find out when the filing is due.

 Here is an exercise for the tax nerd.

(1)  Go to the internet.

(2)  Tell me when a regular vanilla C corporation tax return is due.

(3)  Change the corporate year-end to June 30.

a.    When is that return due?

Yes, the due dates are different. I know because of what I do. Would you have gone to step (3) if I had not pushed you?

Jeffery Lindsay was in prison from 2013 to 2015. He gave his attorney a power of attorney over everything – bank accounts, filing taxes and so on. Lindsay requested the attorney to file and pay his taxes. The attorney assured him he was taking care of it.

He was taking care of Lindsay, all right. He was busy embezzling hundreds of thousands of dollars is what he was doing. Lindsay got wind, sued and won over $700 grand in actual damages and $1 million in punitive damages.

The IRS came in. Why? Because the last thing that the attorney cared about was filing Lindsay’s taxes, paying estimates, any of that. It turns out that Lindsay had filed nothing for years. Lindsay of course owed back taxes. He owed interest on the tax, as he did not pay on time. What stung is that the IRS wanted over $425 grand in penalties.

He did what you or I would do: request that the penalties be abated.

The Court wanted to know the grounds constituting reasonable cause.

Are you kidding me?

Lindsay pointed out the obvious:

         I was in PRISON.”

Here is the Court:

One does not have to be a tax expert to know that tax returns have fixed filing dates and that taxes must be paid when they are due.”

The Court agreed with the IRS and denied reasonable cause.

Lindsay was out hundreds of thousand of dollars in penalties.

I consider the decision the logical conclusion of Boyle. I also think it is a bad decision, and it encapsulates, highlights and magnifies the absurdity of Boyle using the logic of “reductio ad absurdum.”

Our case this time was Lindsay v United States, USDC No 4:19-CV-65.

Incompetent Employees And IRS Penalties

 

“Taxes are what we pay for civilized society.” Compania General De Tabacos de Filipinas v. Collector, 275 U.S. 87, 100 (1927) (Taft, C.J.). For good reason, there are few lawful justifications for failing to pay one's taxes. Plaintiff All Stacked Up Masonry, Inc. (“All Stacked Up”), a corporation, believes it has such an excuse. It brings this suit to challenge penalties and interest assessed by the Internal Revenue Service (“IRS”) following its failure to file the appropriate payroll tax documents and its failure to timely pay payroll tax liabilities for multiple tax periods.

The above is how the Court decision starts.

Here are the facts from 30,000 feet.

·      The company provides masonry services.

·      The company got into payroll tax issues from 2013 through 2015.

·      The company paid over $95 thousand in penalties and interest.

·      It now wanted that money back. To do so it had to present reasonable cause for how it got into this mess in the first place.

Proving reasonable cause is not easy, as the IRS keeps shrinking the universe of reasonable cause.  An example is an accountant missing a timely extension. There is a case out there called Boyle, and the case divides an accountant’s services into two broad camps:

·      Advice on technical issues, and

·      Stuff a monkey could do.

Let’s say that CTG Galactic Command is planning a corporate reorganization and we blow a step, causing significant tax due. Reliance on us as your advisors will probably constitute reasonable cause, as the transaction under consideration was complex and required specialized expertise. Let’s say however that we fail to extend the corporate return – or we file it two days after its extended due date. Boyle stands for the position that anyone can google when the return was due, meaning that relying on us as your tax advisors to comply with your filing deadline is not reasonable.

As a practitioner, I have very little patience with Boyle. We prepare well over a thousand individual tax returns, not to mention business, nonprofit, payroll, sales tax, paper airplanes and everything in between. Visit this office during the last few days before April 15th, for example, and you can feel the tension like the hum from an electrical transformer. What returns are finished? What returns are only missing an item or two and can hopefully be finished? What returns cannot possibly be finished? Do we have enough information to make an educated guess at tax due? Who is calling the client?  Who is tracking and recording all this to be sure that nothing is overlooked? Why do we do this to ourselves?

Yeah, mistakes happen in practice. Boyle just doesn’t care. Boyle holds practitioners to a standard that the IRS itself cannot rise to. I have several files in my office just waiting, because the IRS DOES NOT KNOW WHAT TO DO. I brought in the Taxpayer Advocate recently because IRS Kansas City botched a client. We filed an amended return in response to a Notice of Deficiency the client did not inform us about. The amended must have appeared as “too much work” to some IRS employee, and we were informed that Kansas City inexplicably closed the file. This act occurred well before but was fortuitously masked by subsequent COVID issues. The after-effects were breathtaking, with lien notices, our requests for releases, telephone calls with IRS attorneys, Collection’s laughable insistence on a payment plan, and – ultimately – a delay on the client’s refinancing. IRS incompetence cumulatively cost me the better part of a day’s work. Considering what I do for a living, that is time and money I cannot get back

I should be able to bill the IRS for wasting my time over stuff a monkey could do.

The Advocate did a good job, by the way.

Let’s get back to All Stacked Up, the company whose payroll issues we were discussing.

The owner fell on ice and suffered significant injuries. This led to the owner relying on an employee for tax compliance. That reliance was misplaced.

·      The first two quarterly payroll returns for 2013 were filed late.

·      The fourth quarter, 2013 return would have been due January 31, 2014. It was not filed until July 13, 2015.

·      None of the 2014 quarterly returns were filed until the summer of 2015.

·      To complete this sound track, the payroll tax deposits were no timelier than the filing of the returns themselves.

Frankly, the company should just have let its CPA firm take care of the matter. Had the firm botched the work this badly, at least the company would have a possible malpractice lawsuit.

The company pleaded reasonable cause. The owner was injured and tried to delegate the tax duties to someone during his absence. Granted, it did not go well, but that does mean that the owner did not try to behave as a prudent business person.

I get the argument. All Stacked Up is not Apple or Microsoft, with acres and acres of lawyers and accountants. They did the best they could with the (clearly limited) resources they had.

The company appealed the penalties. IRS Appeals was willing to compromise – but only a bit. Appeals would abate 16.66% of the penalties and related interest. This presented a tough call: accept the abatement or go for it all.

The company went for it all.

Here is the Court:

Applying Boyle to this case, it is clear as a matter of law that retention of an employee or software to prepare and remit tax filings, make required deposits, and tender payments cannot, in itself, constitute “reasonable cause” for All Stacked Up’s failure to satisfy those tax obligations. The employee’s failures are All Stacked Up’s failures, no matter how prudent the delegation of those duties may have been.”

And there is full Boyle: we don’t care about your problems and you doing your best with the resources available. Your standard is perfection, and do not ask whether we hold ourselves to the same standard.

I wonder if that employee is still there.

I mean the one at IRS Kansas City.

Our case this time was All Stacked Up v U.S., 2020 PTC 340 (Fed Cl 2020).