Cincyblogs.com
Showing posts with label employee. Show all posts
Showing posts with label employee. Show all posts

Monday, June 26, 2023

Failing To Take A Paycheck

I am looking at a case involving numerous issues. The one that caught my attention was imputed wage income from a controlled company in the following amounts:

2004                    $198,740

2005                    $209,200

2006                    $220,210

2007                    $231,800

2008                    $244,000

Imputed wage income means that someone should have received a paycheck but did not.

Perhaps they used the company to pay personal expenses, I think to myself, and the IRS is treating those expenses as additional W-2 income. Then I see that the IRS is also assessing constructive dividends in the following amounts:

2004                    $594,170

2005                    $446,782

2006                    $375,246

2007                    $327,503

2008                    $319,854 

The constructive dividends would be those personal expenses.

What happened here?

Let’s look at the Hacker case.

Barry and Celeste Hacker owned and were the sole shareholders of Blossom Day Care Centers, Inc., an Oklahoma corporation that operated daycare centers throughout Tulsa. Mr. Hacker also worked as an electrician, and the two were also the sole shareholders of another company - Hacker Corp (HC).

The Hackers were Blossom’s only corporate officers. Mrs. Hacker oversaw the workforce and directed the curriculum, for example, and Mr. Hacker was responsible for accounting and finance functions.

Got it. She sounds like the president of the company, and he sounds like the treasurer.

For the years at issue, the Hackers did not take a paycheck from Blossom.

COMMENT: In isolation, this does not have to be fatal.

Rather than pay the Hackers directly, Blossom made payments to HC, which in turn paid wages to the Hackers.

This strikes me as odd. Whereas it is not unusual to select one company out of several (related companies) to be a common paymaster, generally ALL payroll is paid through the paymaster. That is not what happened here. Blossom paid its employees directly, except for Mr. and Mrs. Hacker.

I am trying to put my finger on why I would do this. I see that Blossom is a C corporation (meaning it pays its own tax), whereas HC is an S corporation (meaning its income is included on its shareholders’ tax return). Maybe they were doing FICA arbitrage. Maybe they did not want anyone at Blossom to see how much they made.  Maybe they were misadvised.

Meanwhile, the audit was going south. Here are few issues the IRS identified:

(1)  The Hackers used Blossom credit cards to pay for personal expenses, including jewelry, vacations, and other luxury items. The kids got on board too, although they were not Blossom employees.

(2)  HC paid for vehicles it did not own used by employees it did not have. We saw a Lexus, Hummer, BMW, and Cadillac Escalade.

(3) Blossom hired a CPA in 2007 to prepare tax returns. The Hackers gave him access to the bank statements but failed to provide information about undeposited cash payments received from Blossom parents.

NOTE: Folks, you NEVER want to have “undeposited” business income. This is an indicium of fraud, and you do not want to be in that neighborhood.

(4)  The Hackers also gave the CPA the credit card statements, but they made no effort to identify what was business and what was family and personal. The CPA did what he could, separating the obvious into a “Note Receivable Officer” account. The Hackers – zero surprise at this point in the story - made no effort to repay the “Receivable” to Blossom.  

(5) Blossom paid for a family member’s wedding. Mr. Hacker called it a Blossom-oriented “celebration.”  

(6) In that vein, the various trips to the Bahamas, Europe, Hawaii, Las Vegas, and New Orleans were also business- related, as they allowed the family to “not be distracted” as they pursued the sacred work of Blossom.

There commonly is a certain amount of give and take during an audit. Not every expense may be perfectly documented. A disbursement might be coded to the wrong account. The company may not have charged someone for personal use of a company-owned vehicle. It happens. What you do not want to do, however, is keep piling on. If you do – and I have seen it happen – the IRS will stop believing you.

The IRS stopped believing the Hackers.

Frankly, so did I.

The difference is, the IRS can retaliate.

How?

Easy.

The Hackers were officers of Blossom.

Did you know that all corporate officers are deemed to be employees for payroll tax purposes? The IRS opened a worker classification audit, found them to be statutory employees, and then went looking for compensation.

COMMENT: Well, that big “Note Receivable Officer” is now low hanging fruit, isn’t it?

Whoa, said the Hackers. There is a management agreement. Blossom pays HC and HC pays us.

OK, said the IRS: show us the management agreement.

There was not one, of course.

These are related companies, the Hackers replied. This is not the same as P&G or Alphabet or Tesla. Our arrangements are more informal.

Remember what I said above?

The IRS will stop believing you.

Petitioner has submitted no evidence of a management agreement, either written or oral, with Hacker Corp. Likewise, petitioner has submitted no evidence, written or otherwise, as to a service agreement directing the Hackers to perform substantial services on behalf of Hacker Corp to benefit petitioner, or even a service or employment agreement between the Hackers and Hacker Corp.”

Bam! The IRS imputed wage income to the Hackers.

How bad could it be, you ask. The worst is the difference between what Blossom should have paid and what Hacker Corp actually paid, right?

Here is the Court:

Petitioner’s arguments are misguided in that wages paid by Hacker Corp do not offset reasonable compensation requirements for the services provided by petitioner’s corporate officers to petitioner.”

Can it go farther south?

Respondent also determined that petitioner is liable for employment taxes, penalties under section 6656 for failure to deposit tax, and accuracy-elated penalties under section 6662(a) for negligence.”

How much in penalties are we talking about?

2005                    $17,817

2006                    $18,707

2007                    $19,576

2008                    $20,553

I do not believe this is a case about tax law as much as it is a case about someone pushing the boundary too far. Could the IRS have accepted an informal management agreement and passed on the “statutory employee” thing? Of course, and I suspect that most times out of ten they would. But that is not what we have here. Somebody was walking much too close to the boundary - if not walking on the fence itself - and that somebody got punished.

Our case this time was Blossom Day Care Centers, Inc v Commissioner, T.C. Memo 2021-86.


Sunday, March 26, 2023

Renting a Home Office To An Employer

A client asked about the home office deduction last week.

This deduction has lost much of its punch with the Tax Cuts and Jobs Act of 2017. The reason is that employee home office deductions are a miscellaneous itemized deduction, and most miscellaneous itemized deductions have been banned for the next two-plus years. 

The deduction still exists for self-employeds, however, including partners in a partnership or members in an LLC. Technically there is one more hoop for partners and members, but let’s skip that for now.

Say you are working from home. You have a home office, and it seems to pass all the bells-and-whistles required for a tax deduction. Can you deduct it?

Depends. On what? On how you are compensated.

(1) If you are a W-2 employee, then you have no deduction.

(2) If you receive a 1099 (think gig worker), then you have a deduction.

Seems unfair.

Can we shift those deductions to the W-2 employer? Would charging rent be enough to transform the issue from being an employee to being a landlord?

There was a Tax Court case back in the 1980s involving the tax director of a public accounting firm in Phoenix (Feldman). His position involved considerable administrative work, a responsibility difficult to square with being accessible to staff at work while also maintaining confidentiality on private firm matters.

Feldman built a house, including a dedicated office.  He worked out an above-market lease with his firm. He then deducted an allocable share of everything he could against that rent, including maid service.

No surprise, Feldman and the IRS went to Tax Court.

Let’s look at the Code section under dispute:

Sec 280A Disallowance of certain expenses in connection with business use of home, rental of vacation homes, etc.

(a)  General rule.

Except as otherwise provided in this section, in the case of a taxpayer who is an individual or an S corporation, no deduction otherwise allowable under this chapter shall be allowed with respect to the use of a dwelling unit which is used by the taxpayer during the taxable year as a residence.

Thanks for the warm-up, said Feldman., but let’s continue reading:

      Sec 280A(c)(3) Rental use.

Subsection (a) shall not apply to any item which is attributable to the rental of the dwelling unit or portion thereof (determined after the application of subsection (e).

I am renting space to the firm, he argued. Why are we even debating this?

The lease is bogus, said the IRS (the “respondent”).

Respondent does not deny that under section 280A a taxpayer may offset income attributable to the rental of a portion of his home with the costs of producing that rental income. He contends, however, that the rental arrangement here is an artifice arranged to disguise compensation as rental income in order to enable petitioner to avoid the strict requirements of section 280A(c)(1) for deducting home office expenses. Because there was no actual rental of a portion of the home, argues respondent, petitioner must qualify under section 280A(c)(1) before he may deduct the home office expenses.

Notice that the IRS conceded that Feldman was reading the Code correctly. They instead were arguing that he was violating the spirit of the law, and they insisted the Court should observe the spirit and not the text.

The IRS was concerned that the above-market rent was disguised compensation (which it was BTW). Much of tax practice is follow-the-leader, so green-lighting this arrangement could encourage other employers and employees to shift a portion of their salaries to rent. This would in turn free-up additional tax deductions to the employee - at no additional cost to the employer but at a cost to the fisc.

The IRS had a point. As a tax practitioner, I would use this technique - once blessed by the Court – whenever I could.

The Court adjusted for certain issues – such as the excess rent – but decided the case mostly in Feldman’s favor.

The win for practitioners was short-lived. In response Congress added the following to the Code:

      (6)  Treatment of rental to employer.

Paragraphs (1) and (3) shall not apply to any item which is attributable to the rental of the dwelling unit (or any portion thereof) by the taxpayer to his employer during any period in which the taxpayer uses the dwelling unit (or portion) in performing services as an employee of the employer.

An employer can pay rent for an employee’s office in home, said Congress, but we are disallowing deductions against that rental income.

Our case this time was Feldman v Commissioner, 84 T.C. 1 (U.S.T.C. 1985).

 

Tuesday, January 24, 2023

A Ghost Preparer Story

 

I came across a ghost preparer last week.

I rarely see that.

A ghost preparer is someone who prepares a tax return for compensation (me, for example) but who does not sign the return.

This is a big no-no in tax practice. The IRS requires all paid tax preparers to obtain an identification number (PTIN, pronounced “pea tin”) and disclose the same on returns. The IRS can track, for example, how many returns I signed last year via my PTIN. There are also mandates that come with the CPA license.

Why does the ghost do this?

You know why.

It started with a phone call.

Client: What do you know about the employee retention credit?

Me: Quite a bit. Why do you ask?”

Client: I had someone prepare refunds, and I want to know if they look right.”

You may have heard commercials for the ERC on the radio These credits are “for up to $26,000 per employee” but you “must act now.”

Well, yes, it can be up to $26,000 per employee. And yes, one should act soon, because the ERC involves amending tax returns. Generally, one has only three years to amend a return before the tax period closes. This is the statute of limitations, and it is both friend and foe. The IRS cannot chase you after three years, but likewise you cannot amend after the same three years.

The ERC was in place for most of 2020 and for 9 months of 2021. If you are thinking COVID stimulus, you are right. The ERC encouraged employers to retain employees by shifting some of the payroll cost onto the federal government.

Me: I thought you did not qualify for the ERC because you could not meet the revenue reduction.” 

         Client: They thought otherwise.”

         Me: Send it to me.”

He did.

I saw refunds of approximately $240,000 for 2020. I also remember our accountant telling me that the client could not meet the revenue reduction test for 2020. Revenues went down, yes, but not enough to qualify for the credit.

COMMENT: There are two ways to qualify for the ERC: revenue reduction or the mandate. The revenue reduction is more objective, and it requires a decrease in revenue from 2019 (50% decrease for the 2020 ERC; 20% decrease for the 2021 ERC). The second way – a government COVID mandate hobbling the business – does not require revenue reduction but can be more difficult to prove. A restaurant experiencing COVID mandates could prove mandate relatively easily. By contrast, a business experiencing supply-chain issues probably experienced COVID mandates indirectly. The business would likely need its suppliers’ cooperation to show how government mandates closed their (i.e., the suppliers’) doors.

I had our accountant locate the 2020 accounting records. We reviewed the revenue reduction.

The client did not make it.

I called.

Me: Did they say that you qualified under the mandate test?"

         Client: They said I qualified under revenue reduction."

         Me: But you don’t. How could they not tell?"

         Client: Because they never looked at it."

         Me: Then how ….?"

Client: They asked if I had a revenue decline and I said yes. They took my answer and ran with it."

Why would someone do this?

Because that someone works on commission.

There is incentive to maximize the refund, whether right or not.

I was looking at a refund of almost a quarter million dollars.

That would have been a nice commission.

No, the client is not filing those amended returns. He realized the con. He also realized that he had no argument upon IRS audit. He would have to return the money, plus whatever penalties they would layer on. I could no more save him than I could travel to Mars.

He now also understands why they never signed those returns.

Ghosts.


Saturday, November 19, 2022

Can A Severance Be A Gift?


I am looking at a case wondering why a tax practitioner would take it to Tax Court.

Then I noticed that it is a pro se case.

We have talked about this before: pro se means that the taxpayer is representing himself/herself. Technically that is not correct (for example, someone could drag me in and still be considered pro se), but it is close enough for our discussion.

Here is the issue:

Can an employer make a nontaxable gift to an employee?

Jennifer Fields thought so.

She worked at Paragon Canada from 2009 to 2017. Apparently, she was on good terms with her boss, as the company …

·      Wired her 35,000 Canadian dollars in 2012

·      Wired her $53,020 in 2014 to help with the down payment on a house in Washington state.

I am somewhat jealous. I am a career CPA, and CPA firms are not known for … well, doing what Paragon did for Jennifer.

She separated from Paragon in 2017.

They discussed a severance package.

Part of the package was forgiveness of the loan arising from those wires.

Forgiveness here does not mean what it means on Sunday. The company may forgive repayment, but the IRS will still consider the amount forgiven to be taxable income. The actual forgiveness is therefore the after-tax amount. If one’s tax rate is 25%, then the actual forgiveness would be 75% of the amount forgiven. It is still a good deal but not free.

Paragon requested and she provided a Form W-9 (the form requesting her social security number).

Well, we know that she will be getting a W-2 or a 1099 for that loan.

A W-2 would be nice. Paragon would pick-up half of the social security and Medicare taxes. If she is really lucky, they might even gross-up her bonus to include the taxes thereon, making the severance as financially painless as possible.

She received a 1099.

Oh well.

She left the 1099 off her tax return.

The IRS computers caught it.

Because … of course.

Off to Tax Court they went.

This is not highbrow tax law, folks. She worked somewhere. She received a paycheck. She left work. She received a final paycheck. What is different about that last one?

·      She tried to get Paragon to consider some of her severance as a gift.

The Court was curt on this point. You can try to be a bird, but you better not be jumping off tall buildings thinking you can fly.

·      She was good friends with her boss. She produced e-mails, text messages and what-not.

That’s nice, said the Court, but this is a job. There is an extremely high presumption in the tax Code that any payment to an employee is compensatory.

But my boss and I were good friends, she pressed. The law allows a gift when the relationship between employer and employee is personal and the payment is unrelated to work.

Huh, I wonder what that means.

Anyway, the Court was not buying:

Paragon’s inclusion of the disputed amount in the signed and executed severance agreement and the subsequent issuance of a Form 1099-MISC indicates that the payments were not intended to be a gift.”

She really did not have a chance.

The IRS also wanted penalties. Not just your average morning-drive-through penalties, no sir. They wanted the Section 6662(a) “accuracy related” penalty. Why? Well, because that penalty is 20%, and it is triggered if the taxpayer omits enough income to underpay tax by the greater of $5 grand or 10% of what the tax should have been.

Think biggie size.

The Court agreed on the penalty.

I was thinking what I would have done if Jennifer had been my client.

First, I would have explained that her chance of winning was almost nonexistent.

COMMENT: She would have fired me then, realistically.

Our best course would be to resolve the matter administratively.

I want the penalties dropped.

That means we are bound for Appeals. There is no chance of getting that penalty dropped before then.

I would argue reasonable cause. I would likely get slapped down, but I would argue. I might get something from the Appeals Officer.

Our case this time was Fields v Commissioner, T.C. Summary Opinion 2022-22.

 

Sunday, September 19, 2021

Receiving An IRS Lock-In Letter

 

A client recently picked up his personal tax return. He asked to see me.

There was tax due with the return. I thought he had adjusted his withholding to increase his take-home pay, as he had spoken to me of financial stress. I am not a fan of doing this, as tax is due whether one withholds or not.   

He could not have tax due with his return, he explained, as he had received a lock-in letter from the IRS.

There is something I do not often see.

There are two versions of the lock-in letter: one sent to the employee and another to the employer. The IRS is telling both that it wants additional withholding from each paycheck, commonly meaning single withholding with no dependents.

The lock-in surprised me, as my client is not one to game the system. What he did was fall behind on his taxes due to a failed business. There are liens – IRS and private - that he is working through.

The IRS sends the employee a letter informing him/her that his/her withholdings are too low. The IRS wants the employee to self-adjust by increasing their withholding.

If that fails, the IRS sends the employer a letter. An employer has 60 days from the date of the letter to unilaterally adjust the employee’s withholdings.

The employee can quit, but the lock is good for 12 months. The employee will have to go somewhere else for a year before returning if he/she wishes to avoid the lock.

The 60 days has two purposes:

(1)  To allow the employer time to make the changes, and 

(2)  To prompt the employee to contact the IRS. If so – and if the employee can persuade the IRS – the IRS may modify the lock.

If the employee keeps his/her nose clean, he/she can request the IRS remove the lock-in. Figure that it will take about three years of tax returns, however, so it is best to avoid the lock altogether.

The employer is extremely unlikely to buck the IRS, as the employer might then draw surrogate liability. One might be a valued employee, but one is not that valued. 

Let’s look at a case.

Charles G worked for Volvo Trucks North America (VTNA). He submitted a W-4 to VTNA claiming that he was exempt from income tax withholding. He also requested VTNA to stop withholding social security taxes.

VTNA was surprisingly tolerant. It spotted Charles a 99-dependent W-4 (affecting income tax withholding), although it could not do anything about the social security.

Charles went a couple of years or so before the IRS contacted him. He blew it off, so the IRS sent VTNA a lock-in letter.

Charles went ballistic.

Charles accused the IRS and VTNA of “acting in violation of the Racketeer Influenced and Corrupt Organizations Act (RICO).”

Wow. I wonder how it went come employee review time.

The Court of course dismissed Charles’ claim against VTNA. In general, an employer must follow an employee’s request concerning withholding. If the employee asserts that he/she is exempt from withholding, then the employer must comply with such request unless certain situations occur. A lock-in letter is one of those situations.

It sounds rather self-evident, truthfully.

It also sounds like Charles was a bit of a tax protestor. A word of advice: don’t go there with Charles. Your chances of success are between zero and none, and the list of dead bodies on that hill stretches interminably. Several years ago, we represented a business having an officer the IRS considered a protestor. I did not agree with the IRS on this, but I admit that he was getting close to the line.  The audit was … unpleasant. There was no question that school was in session, and the IRS was looking to teach a lesson.

Our case this time was Giles v Volvo Trucks of North America, 551 F. Supp 2nd 359.

Sunday, June 20, 2021

Downside Of Not Issuing 1099s


Let’s be honest: no one likes 1099s.

I get it. The government has conscripted us – business owners and their advisors – into unpaid volunteers for the IRS. Perhaps it started innocently enough, but with the passage of years and the accretion of reporting demands, information reporting has become a significant indirect tax on businesses.

It’s not going to get better. There is a proposal in the White House’s Green Book, for example, mandating banks to report gross deposit and disbursement account information to the Treasury.

Back to 1099s.

You see it all the time: one person pays another in cash with no intention – or ability – to issue a 1099 at year-end.

What can go wrong?

Plenty.

Let’s look at Adler v Commissioner as an example.

Peter Adler owned a consulting company. He had a significant client. He would travel for that client and be reimbursed for his expenses.

The accounting is simple: offset the travel expenses with the reimbursements. Common sense, as the travel expenses were passed-on to the client.

However, in one of the years Peter incurred expenses of approximately $44 thousand for construction work.

The Court wondered how a consultant could incur construction expenses.

Frankly, so do I.

For one reason or another Peter could not provide 1099s to the IRS.

One possible reason is that Peter made his checks out to a corporation. One is not required to issue 1099s to an incorporated business. Peter could present copies of the cancelled checks. He could then verify the corporate status of the payee on the secretary of state’s website.

Nah, I doubt that was the reason.

Another possibility is that Peter got caught deducting personal expenses. Let’s assume this was not the reason and continue our discussion.

A third possibility is that Peter went to the bank, got cash and paid whoever in cash. Paying someone in cash does not necessarily mean that you will not or cannot issue a 1099 at year-end, but the odds of this happening drop radically.

Peter had nothing he could give the Court. I suppose he could track down the person he paid cash and get a written statement to present the Court.

Rigghhhtttt ….

The Court did the short and sweet: they disallowed the deduction.

Could it get worse?

Fortunately for Peter, it ended there, but – yes – it can get worse.

What if the IRS said that you had an employee instead of a contractor? You are now responsible for withholdings, employer matching, W-2s and so on.

COMMENT: You can substitute “gig worker” for contractor, if you wish. The tax issues are the same.

Folks, depending upon the number of people and dollars involved, this could be a bankrupting experience.

Hold on CTG, say you. Isn’t there a relief provision when the IRS flips a contractor on you?

There are two.

I suspect you are referring to Section 530 relief.

It provides protection from an IRS flip (that is, contractor to employee) if three requirements are met:

1.    You filed the appropriate paperwork for the relationship you are claiming exists with the service provider.

2.    You must be consistent. If Joe and Harry do the same work, then you have to report Joe and Harry the same way.

3.    You have to have a reasonable basis for taking not treating the service provider as an employee. The construction industry is populated with contractors, for example.

You might be thinking that (3) above could have saved Peter.

Maybe.

But (1) above doomed him.

Why?

Because Peter should have issued a 1099. He had a business. A business is supposed to issue a 1099 to a service provider once payments exceed $600.

There was no Section 530 relief for Peter.

I will give you a second relief provision if the IRS flips a contractor on you. 

Think about the consequences of this for a second.

(1)  You were supposed to withhold federal income tax.

(2)  You were supposed to withhold social security.

(3)  You were supposed to match the social security.

(4)  You were supposed to remit those withholdings and your match to the IRS on a timely basis.

(5)  You were supposed to file quarterly employment reports accounting for the above.

(6)  You were supposed to issue W-2s to the employee at year-end.

(7)  You were supposed to send a copy of the W-2 to the Social Security Administration at year-end.

(8)  Payroll has some of the nastiest penalties in the tax Code.

This could be a business-shuttering event. I had a client several years ago who was faced with this scenario. The situation was complicated by fact that the IRS considered one of the owners to be a tax protestor. I personally did not think the owner merited protestor status, as he was not filing nonsense appeals with the IRS or filing delaying motions with the Tax Court. He was more …  not filing tax returns.  Nonetheless, I can vouch that the IRS was not humored.

Back to relief 2. Take a look at this bad boy:

§ 3509 Determination of employer's liability for certain employment taxes.


(a)  In general.

If any employer fails to deduct and withhold any tax under chapter 24 or subchapter A of chapter 21 with respect to any employee by reason of treating such employee as not being an employee for purposes of such chapter or subchapter, the amount of the employer's liability for-

(1)  Withholding taxes.

Tax under chapter 24 for such year with respect to such employee shall be determined as if the amount required to be deducted and withheld were equal to 1.5 percent of the wages (as defined in section 3401 ) paid to such employee.

(2)  Employee social security tax.

Taxes under subchapter A of chapter 21 with respect to such employee shall be determined as if the taxes imposed under such subchapter were 20 percent of the amount imposed under such subchapter without regard to this subparagraph .

Yes, you still owe federal income and social security, but it is a fraction of what it might have been. For example, you should have withheld 7.65% from the employee for social security. Section 3509(a)(2) gives you a break: the IRS will accept 20% of 7.65%, or 1.53%.

Is it great?

Well, no.

Might it be the difference between staying in business and closing your doors?

Well, yes.

Sunday, November 15, 2020

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).