Penalties For Cash Reporting Failures

 

It would be a vast understatement to say that the plucky Rebellion had software issues this busy season.

We saw (some of) it coming … given the merger and all. Short of Excel and Word, there was little overlap between our softwares - that is, our preparation software, research software, time reporting, invoicing and receipt, monitoring the accounting practice and whatnot.

We are still working through the shock.

And I see a Tax Cout decision issued about a week ago concerning software.

I can tell you before reading it how the Court will decide:

Software – unless involving matters exceeding the minds of mortal men – will not save one from penalties. If one purchases and installs software, one is under obligation to learn and master it.

My thoughts?

I am divided. An ordinary taxpayer does not – should not - need my services. Reach a certain point though, and a tax professional becomes as necessary as a primary physician or a dentist.

Still, the Code has become increasingly complex since I came out of school. The very computerization that has allowed professionals to streamline and systematize their work has simultaneously allowed the Congressional tax committees to draft and score increasing complex and near-unworkable changes to the Code. Far too many of these changes can potentially reach ordinary taxpayers. That taxpayer would probably not know that he/she wandered into a minefield. He/she would learn of it when the penalty notice arrived, however. The IRS (and too often the courts) presume that you have a graduate degree in taxation – ignorance of the law is no excuse and all that flourish. They do not care that you don’t.

Dealers Auto Auction of Southwest LLC (Dealers) was an Arizona company selling vehicles through auction houses. It frequently received cash in the ordinary conduct of its business. Not surprisingly, the cash from a sale would often exceed $10,000.

There is a Code section involved here:

          Section 6050I

(a)  Cash receipts of more than $10,000

Any person

(1)  Who is engaged in a trade or business, and

(2)  Who in the course of such trade or business, receives more than $10,000 in cash in 1 transaction (or 2 or more related transactions),

shall make the return described in subsection (b) with respect to such transaction (or related transactions) at such time as the Secretary may by Regulations prescribe.

Once Sec 6050I is triggered, the company files Form 8300 with the IRS. It is an information return (no taxes go with it), but there are penalties for failure to file the return.

Not surprisingly, it has its own rules and subrules.

You know the Forms 8300 were an issue for Dealers.

They bought software (AuctionMaster) to deal with it.

They bought the software after flubbing the 2014 Form 8300 filings. The IRS assessed penalties of over $21 grand, and Dealers realized that buying software was cheaper than paying penalties.

And … the IRS was back in 2016.

Why?

Dealers filed 116 Forms 8300. The IRS argued that Dealers should have filed 382.

The IRS wanted over $118 grand in penalties.

Yipes!

Here is the Court:

Dealers Auto was not immediately aware of its failures. Instead, it was not until the Commissioner began the examination that Dealers Auto became aware of its noncompliance.”

Dealers was blindsided.

It took immediate steps:

·       It contacted the software provider and learned that improved aggregation features were available starting in 2017 (the year following the audit year).

·       Dealers quizzed the auditor on the subtleties of Form 8300 and its filing requirements.

·       Dealers changed its procedures and internal control for filing 8300s.

·       Dealers changed to electronic filing of the 8300s. They let the software cook.

No way the IRS was going to retract that $118 grand-plus assessment, though.

Dealers appealed the penalty. It wanted abatement for reasonable cause.

COMMENT: So would I, frankly.

Dealers’ argument was straightforward: we relied on software, and the software malfunction was outside of our control.

The IRS responded: there was no malfunction. You never mastered the software. If you had, you would have realized that it was not functioning as you thought.

Harsh, methinks. Probably honest, though.

Here is the Court:

Dealers Auto failed to establish that there was a software failure.”

The instructions for the software suggest that the software prepared Forms 8300 for printing, but Dealers Auto asserts that the software files the forms on the user’s behalf.”

Even assuming Dealers Auto met its burden to show a failure beyond the filer’s control, the record does not support a finding that Dealers Auto acted reasonably before or after the failure. For example, Dealers Auto did not establish that it was correctly using the software or that data was being entered correctly into the system.”

Dealers Auto argues that it reasonably believed the software was working as intended because it was generating some information returns. But the record shows that Dealers Auto software prepared only 116 Forms 8300 in 2016. The record also shows that Dealers Auto was required to file at least 212 Forms 8300 in 2014.”

This is going poorly.

What do I see?

I see a small business that was surprised in 2014. It responded with technology, but its familiarity with technology appears limited. It got surprised again. Normally that would indicate recidivism, but I don’t think that is what happened here. I think Dealers had only so many resources to throw at a problem. In addition, they may not have realized the extent of the problem if they were quizzing the IRS auditor on the ins and outs.

What did the Court see?

While it is not necessary to show that Dealers Auto made every data entry correctly, the record offers the Court no insight as to Dealer Auto’s installation, training, or use of the software.”

Here it comes:

Dealers Auto failed to establish that it has reasonable cause for its failure to file information returns for 2016.”

What disappoints me about cases like this is the failure to reward a taxpayer’s effort. Dealers tried. It bought software. It was filing, albeit not as much as it was supposed to. Should it have expended more money and resources on the matter? Clearly, but then I should have played in the NFL and retired as a Hall of Famer. The IRS is punishing Dealers like a scofflaw who did not care, made things up and never intended to follow the rules. To me, applying the same penalties to both situations is abusive.

Our case this time was Dealers Auto Auction of Southwest LLC v Commissioner, T.C. Memo 2025-38.

Is This Reasonable?

 

I have long maintained that the IRS is unreasonable by repeatedly disallowing reasonable cause exception to its numerous penalties. Their standard appears to allow little to no room for real-world variables – someone got sick, someone misunderstood the requirements (wow, how could that happen?), technology broke down, and so on.

Mind you, I say this after contacting the IRS – AGAIN – about returns we filed for two clients. In each case the IRS has misplaced the returns, failing its mission, causing needless (and incorrect) notices, and embarrassing us as practitioners. One of these returns will soon celebrate its one-year anniversary. The IRS has had plenty of time to investigate and resolve the matter. I have, and I am just one guy.

However, have a practitioner send a tax return two minutes after midnight on an extended due date and the IRS will penalize his/her tax practice to near bankruptcy. It may be that there was no electricity in the office until that very moment. No matter: there is no reasonable cause for things not functioning perfectly every time every place all the time.

The hypocrisy is almost suffocating. Let’s make the relationship reciprocal – for example, let me send the IRS an invoice for wasting my time – and see how quickly the IRS recoils in terror.

Let’s talk about RSBCO’s recent shout-out to the Supreme Court.

RSBCO was a wealth management company headquartered in Louisiana. It hired someone (let’s call him Smith) with a background in accounting to spearhead its IRS information reporting.

Smith took RSBCO successfully through one filing season.

Unbeknownst to anyone, however, Smith was fighting some dark demons, and the second filing season did not go as well.

Smith unfortunately waited until the final day to electronically file approximately 20,000 information returns using the IRS FIRE system. FIRE sent an automated e-mail that certain files had errors preventing them from being processed and RSBCO should send replacement files. The e-mail went only to Smith, so no one else at RSBCO knew.

Smith – approximately four months later – was able to resume work. He had been diagnosed with clinical depression, having suicidal ideation, and struggling to focus and complete tasks at work.

COMMENT: I am thinking Reg 301.6724-1(c):

(c) Events beyond the filer's control

(1) In general. In order to establish reasonable cause under this paragraph (c)(1), the filer must satisfy paragraph (d) of this section and must show that the failure was due to events beyond the filer's control. Events which are generally considered beyond the filer's control include but are not limited to—

(iv) Certain actions of an agent (as described in paragraph (c)(5) of this section),

Smith saw the e-mails. He corrected the information returns.

QUESTION: What were the errors about? About dashes, that’s what. The IRS wanted dashes added or removed. Approximately 99% of the problem was little more than a spelling bee.

Smith had a successful third filing season.

Except for the $579,198 penalty notice the IRS sent for the information returns from season two.

COMMENT: Methinks that is a bit harsh for not winning a spelling bee.

Smith was still battling his health issues. He hid the penalty notice in his desk.

A few months later RSBCO let Smith go.

The new hire soon found the notice and tried to contact the IRS. The contact number provided was entirely automated, so the hire could never speak with a human being.

COMMENT: Been there, pal.

The IRS – thinking they had been ignored – sent a Final Notice. RSBCO requested a Due Process Hearing.

The Hearing Officer for the CDP hearing mostly waived off RSBCO’s side of the story. After a Solomonic 15-minute reflection, the Officer did offer to abate 25% of the penalty amount.

COMMENT: It’s something.

RSBCO had to decide how to proceed. They decided to pay the IRS $579 grand and pursue the refund administratively.

In December 2018 RSBCO filed a Claim for Refund.

The IRS received it. And then lost it.

Uh huh.

In August 2019 RSBCO filed a lawsuit.

In June 2020 – after irritating the court – the IRS promised RSBCO that it would play fair if they refiled the claim.

RSBCO agreed and withdrew the lawsuit.

In September it filed its Claim for Refund … again.

And the IRS lost it … again.

COMMENT: You see what is going on here, don’t you?

In May 2021 RSBCO filed a second lawsuit in district court.

In September 2022, the jury decided that RSBCO had reasonable cause for penalty abatement.

COMMENT: Will this ever end?

The IRS processed the refund … wait … no, no … that’s wrong. The IRS appealed the district court decision to the Fifth Circuit.

The Fifth Circuit found that jury instructions were flawed. The district court stated that an employee’s mental health - by itself - did not give rise to reasonable cause. The jury was not properly instructed.

QUESTION: I guess the following by the district court judge was unclear to the IRS, which DID NOT object:

Anything else? Anybody want to put your objection [to jury charges] on the record if you’d like objecting to them?”

COMMENT: I can see the confusion. Making out this question is like trying to plumb the metaphysics of James Joyce’s Ulysses. No wonder the IRS failed to object.

In October 2023 RSBCO petitioned the Supreme Court.

Which just declined the petition.

Meaning the Fifth Circuit has the final word.

The Fifth Circuit wants a new trial.

Will this nightmare ever end?

It is … unreasonable.

Our case this time was RSBCO v U.S., US Supreme Court Docket 24-561.

A School And Obamacare Penalties

 

How would you like to get the following notice in the mail?

 

Believe it or not, the IRS sent this to a public school system in Virginia. I am looking at the Tax Court petition as I write this.

This notice is for a Section 6721 penalty, assessed for failure to file certain information forms with the IRS. Common information forms include:

·      Form W-2 (Wage and Tax Statement)

·      Forms(s) 1099 (Interest, Dividends, and numerous others)

·      Form 8027 (Tip Income and Allocated Tips)

·      Forms(s) 1094 & 1095 (Health Insurance)

There is a virtually automatic companion to this penalty - Section 6722 – which assesses another penalty for failure to provide an information form to the recipient.

Combined we are talking over $2.2 million.

To a school?

Let’s go through this.

The school (Arlington) received the above notice dated June 13, 2022.

The second notice (for Section 6722 penalties) was dated June 27, 2022.

The IRS wanted payment by July 12, 2012.

COMMENT: Arlington had an issue. While they knew the IRS was assessing penalties for information returns, they had no idea which information forms the IRS was talking about.

The IRS Revenue Officer (RO) issued a Final Notice of Intent to Levy on July 12, 2022.

COMMENT: The same day?  I have been leaving messages with a Revenue Agent for over two weeks now concerning an individual tax audit, and this RO issued a FINAL on the same day stated in the notice?

COMMENT: There is also a procedural error here. The IRS must issue notices in a certain order, and the RO is not entitled to jump the line and go straight to that FINAL notice.

We learn that this specific RO had previously assessed penalties (without explanation) and filed liens (again, without explanation) on a middle school in the Arlington school system. These miraculously went away before an Appeals hearing could occur.

COMMENT: Sounds like something personal.

On August 10, 2022, Arlington requested a collection due process hearing on the June 13 and June 27 notices. It faced a formidable obstacle, however, as it did not know what the IRS was talking about.

The IRS sent a letter dated December 5, 2022, scheduling an Appeals conference on January 18, 2023. That letter also suggested that Arlington had not filed Forms 1042, which concerns withholding on payments to foreign persons.

COMMENT: Seems an odd one. I would have thought Forms W-2, if anything.

It turns out that the 1042 reference was mistaken.

COMMENT: Clown show.

Arlington (more specifically, Arlington’s attorneys) tried repeatedly to contact the Appeals Officer (AO). It appears that he inadvertently answered his phone one time, and the Appeals conference was moved to January 31, 2023. Arlington still wanted to know what form was costing them over $2.2 million.

The attorneys marched on. They contacted the IRS Practitioner Line, which told them that the penalties might relate to the Affordable Care Act (Obamacare). They also sent a written request to IRS Ogden for explanation and copies of any correspondence concerning the matter.

COMMENT: I’ve done the same. Low probability swing, in my experience.

The attorneys also contacted the Taxpayer Advocate.

Receiving nothing, the attorneys again requested to postpone the Appeals hearing. They learned that two additional penalties had been added. What were the two penalties about? Who knows.

The two late penalties were “abated” before the Appeals hearing on February 10, 2023.

The AO failed to show up to the Appeals hearing on February 10, 2023.

COMMENT: That sounds about right.

At the re-rescheduled hearing on February 24, 2023, the AO wanted to know what Arlington intended to do. Arlington replied that they were still trying to figure out what the penalties were for, and that a little help would be welcome.

That however would require the AO to – gasp – actually work, so he attempted to transfer the case to another AO. He was unsuccessful.

COMMENT: Fire the guy.

On June 30, 2023, the AO sent the attorneys re-generated IRS notices (not copies of originals) proposing $1,1113,000 in penalties for failure to send Forms 1094-C to the IRS and an additional $1,113,000 for failure to provide the same 1094-C to employees.

COMMENT: Finally, we learn the mystery form.

Arlington (really, its attorneys) learned that the IRS had listed a “Lang Street” address for correspondence. Lang Street was never Arlington’s address and was only one of the middle schools in the district. It was, however, the middle school which the RO had liened earlier in our story.

While talking to the AO on June 30, 2023, the attorneys requested additional time to submit a penalty abatement request.  The AO allowed 14 days.

COMMENT: Really? This is the school’s summer recess, no one is there, and you expect people to dig up years-old paperwork in 14 days?

Once again, the AO refused to answer numerous calls and faxes.

The attorneys – frustrated – contacted the AO’s manager. The manager gave them additional time.

On August 21, 2023, Arlington received a mysterious IRS letter about a claim filed on or about February 23, 2023. Problem: Arlington had not filed any such thing.

The attorneys sent a copy of the mystery notice to the AO.

On September 13, 2023, the AO told the attorneys that he had closed the case and issued a Notice of Determination.

COMMENT: This is the “90-day letter” and one’s entrance ticket to the Tax Court.

The attorneys asked why the NOD. The AO explained that he could not provide a penalty abatement while the underlying Obamacare forms remained unfiled.

Uh huh.

By the way, while the AO verbally communicated that a NOD had been issued, Arlington never received it. It appears - best I can tell – that the NOD is stuck at a processing facility.

COMMENT: Fits the rest of the story.

So, what happened with those forms?

It turns out that Arlington sent employees their copies of the Obamacare forms on or about February 28, 2020.

COMMENT: Well, there goes one of the two penalties.

Arlington was going to send the IRS copies on March 16, 2020.

What happened at this point in 2020?

The Governor of Virginia closed all schools for two weeks over COVID-19.

He then closed the schools through the rest of the school year.

On March 30, 2020, Arlington requested an extension of time to file those Obamacare forms with the IRS.

Virtually no one was at the school. People were working remotely, if possible. The school was trying to figure out how to even pay its employees when everyone was remote.

Yeah, I suspect those forms were never sent.

Heck of a reasonable cause, I would say.

And fire the guy.

A Too Rare Taxpayer Win Over Foreign Reporting

I have become cynical about IRS penalties.

Like many accountants, I initially learned that penalties were in the system as a deterrent. If one complies with reporting responsibilities, penalties should not enter the picture. If they do, they surely would be for ministerial causes (think late payment of an estimated tax) and minor, and – if somehow major – waivable upon showing reasonable cause for the mistake.  

Poppycock.

Congress has been raising and creating penalties for decades to “pay for” their tax bills. I would also argue that the IRS has used penalties as a backstop to its funding, especially during Republican budget stringency after the Lois Lerner fiasco.  

The IRS often assesses penalties automatically, without anyone even glancing at your return. This transfers tax administration from the IRS to you – and then by extension – to me. Say that you have a reportable interest in a foreign corporation. The IRS says you must file a certain information report. I get it: the IRS wants to know what is going on. You file the report, but you file it late. Why late? Who knows. Your accountant was on health leave. You were misadvised. You were never advised because you did not recognize it as a tax-sensitive issue. You will – soon enough – get an automatic IRS notice for a $10,000 penalty – or more. You complied, but not fast enough.

Reasonable cause?

Depends on who defines reasonable. As a practicing tax CPA for decades, I am much more open to reasonable cause. Why? I am closer to the day-to-day, so I do not have the anesthesia of distance and disinterest. Things ... just … happen. No one likes paying, but let’s not use that same brush to accuse one of gaming the system.

Let’s take a look at Wrzesinski.

We will call him “W” to keep our sanity.

W was born in Poland. He moved to the United States when he was 19 years old.

A few years later his mom, who still lived in Poland, won the Polish lottery.

Sweet.

Mom gifted him $830,000 over a couple of years.

W knew about U.S. tax. He contacted his tax advisor to ask what the consequences would be. His advisor (G) correctly told him that the gift would not be taxable, but incorrectly told him that no further reporting was required.

I know that G was wrong, but how could the IRS expect W to know that?

Fast forward a few years and W wanted to make a gift to his godson in Poland. He did an internet search, at which time he realized that – while not taxable – reporting was still required. He realized this situation as his own years before, and he contacted an attorney with expertise in foreign tax matters.

W got into an IRS program for late filing of certain foreign-related returns. The IRS would tread lightly if one had reasonable cause, and both W and his attorney thought he had reasonable cause to spare.

I agree.

The IRS came back with its automatic penalties: they wanted $87,500 for one year and $120,000 for the second.

Their reason?

The Notices stated that …

… ignorance of the tax laws was not a basis for penalty abatement under the “reasonable cause” standard and that ordinary business care and prudence require that the taxpayers be aware of their obligations and file or deposit accordingly.”

I would argue the opposite: good faith “ignorance” of tax laws is exactly the basis for the reasonable cause standard. We have more than once huddled here at Galactic Command analyzing tax consequences, especially if planning a transaction. We sometimes disagree. We have run into gaps in tax law, as Congress is churning out this stuff faster than the IRS and the profession can interpret. We have run into contradictions in tax law, especially when the aforesaid gaps are working their way through the courts system. Did I mention that we are all CPAs with varying tax backgrounds? I am, for example, a tax specialist. It is all I do and have done for years.

Consider that there was no tax shelter here, no attempt to avoid reporting income or of claiming bogus deductions. There was a gift from a mother to a son. A gift unfortunately involving some of the most arcane reporting rules embedded in the tax Code. There was no need for the IRS to flog the guy.

W and his attorney protested the penalties.

The IRS lost W’s protest.

Yes, they “lost” his protest.

It took the Taxpayer Advocate to find it.

The IRS abated all but $40 thousand or so of penalties.

W paid it.

And he immediately filed claims for refund.

I like this guy.

The IRS bounced the first claim, saying he did not establish reasonable cause.

You may be figuring out the IRS schtick when in this situation. It is a one-play gamebook: nothing is reasonable. Boyle. Go away.

The IRS bounced the second claim, saying that it was “frivolous.”

Folks, never ever tell a tax practitioner that his/her position is “frivolous.” That is a loaded word in tax practice.

This thing … NO SURPRISE … went to Court.

Let’s fast forward.

In a too-rare taxpayer win, the DOJ conceded the case on February 7, 2023, and requested six to eight weeks to refund W his remaining penalties.

But look at the effort it took.

Our case this time was Krzysztof Wrzesinski v The United States, U.S. District Court, Eastern District of Pennsylvania.

Do You File An Accurate Return Or A Timely Return?

I have alerted the staff here at CTG command center that I prefer and expect to file all business returns, especially passthrough returns, on a timely basis, irrespective of whether we have all required information. Granted, there is some freeplay – we cannot file if we have no information, for example, or if so much information is missing that a filing would not be construed as substantially correct.

The reason?

Penalties for late filing.

Let’s say that you and a partner have an LLC. The return is due in March and can be extended to September. You file an extension but, for whatever reason, do not file the partnership return until December.

What just happened?

(1)  You might think that the return is only 2 months late, as it was extended until September. That is incorrect. You have until September 15 to file the return. Fail to do so, and it is as if you never filed an extension. That return is now late beginning March 16.

(2)  So what? Here is so what: the penalty is $195 per K-1 per month. There are two K-1s: you and a partner. The penalty is $390 per month. Multiply that by the number of months, and you can see how this gets expensive fast.

(3)  You might be able to get out of this penalty. Revenue Procedure 84-35 allows an avenue for small partnerships with 10 or fewer partners, for example. Depending on the facts, however, there may be no easy out. Like fire, you do not want to be playing with this.

There are a hundred variations on the theme. Let me give you one. This one involves an estate tax return. Let’s review the key points, and you decide whether there is cause for a late-filing penalty. 

• The decedent died February 24, 1986.
• On May 6, 1986 the estate was admitted to probate.
• The wife was appointed executrix.
• The estate hired an attorney.
• The estate tax return was due November 24, 1986 (nine months after death). No extension was filed.
• In January, 1987 the executrix filed an inventory with the probate court. Four assets were listed but given no value. One of those assets was an interest in a trust, which asset took on a life of its own. 
• The assets which were valued - that is, excluding the four which were unvalued - were enough the require the filing of a federal estate tax return.
• In 1991 (five years later) the estate filed suit concerning the trust.
• In 1994 the common pleas court entered judgement.
• In 1996 the executrix filed a revised and final accounting with the probate court.
•  In 1997 the estate finally filed a federal estate tax return. 

     The IRS immediately went after late filing penalties. Why wouldn’t it? The tax return was filed more than 10 years after the decedent died.

The gross estate was over $2 million. Those items that could not initially be valued came in around $200 grand.

The IRS charged in and chanted its standard wash-rinse-repeat hymn: the taxpayer cannot escape penalties for the non-extension or late filing of a return pursuant to the Supreme Court’s Boyle decision.

But the estate punched back with reasonable cause: the executrix did not have values for some of the assets that were eventually distributable from the estate. Heck, they had to sue to even get to some of those assets!

What do you think? Is there reasonable cause?

Let me give you a clue: the disputed assets were about 10% of the final estate.

And we come back to a phrase I used early on: “substantially correct.” Tax Regulations require only that the estate return be “as complete as possible.” There are numerous cases where pending litigation – even if the outcome is expected to materially affect the estate’s final tax liability – has not been considered reasonable cause for not filing a return.

The Court pointed out two things:

(1)  The executrix knew (or should have known) early on that the estate was large enough – even excluding the disputed items – to require filing a return.

(2)  She could have paid at least the tax on that amount, or estimated and also included tax on the disputed items.

a.     The Court pointed out that disputed assets were only 10% of the estate.

The executrix did not have reasonable cause. She should have filed and paid something, even if she later had to amend the estate tax return.

My thoughts?

I agree with the Court. I believe the estate was ill-advised. 

There is a sub-story in here concerning the attorney (who thought the accountant was taking care of the estate tax return) and the CPA (who was never told to prepare an estate tax return, at least not until years after the return would have been due). Why didn’t the attorney reach out earlier to the CPA, at least for peace of mind? Who knows? Why didn’t the long-standing CPA – who would have known the decedent - ask about an estate return? Again, who knows?

Our case this time was Estate of Thomas v Commissioner.

COMMENT: I am looking (translation: I printed but have not yet read) a case where a taxpayer did use estimates but still got nailed with penalties. We may come back to that one in the near future.

Issuing 1099s As Retaliation

I continue to be surprised when people use IRS forms as retaliation.

The form of choice tends to be a 1099. The intent – of course – is to provoke an IRS audit.

There was an incessant legal battle several years back at a Cincinnati CPA firm that detonated. I happen to know the parties involved, and I was interested in the use of 1099s as weapons of war. The senior partner in the imbroglio however was not amused with my interest, seemed surprised that so much of the combat was available to one who could search legal records, and told me where to take a long walk. Quite the charmer.

I am reading a case involving doctors in Illinois. There was an anesthesiologist (Nicholas Angelopoulos - “Nick”) who went into business with an orthopedist (Hall).  Hall owned a company (Keystone) which employed Nick and two other doctors.

There was a cost-sharing arrangement among the doctors, which is common enough but which seemed to change without much explanation.

There was question whether Nick and the other two doctors were ever owners of Keystone (an S corporation). There were e-mails, draft shareholder agreements and meeting agendas, and the doctors were charged for equipment purchased by the practice.  Dr Hall, however, maintained that he was the only shareholder.

OK.

There was an LLC called WACHN, comprised of our four doctors plus another and which purchased medical condominiums. Each of the doctors kicked-in $110,000 and the LLC borrowed the rest, although the doctors had to personally guarantee the debt. Nick said that he never signed the operating agreement and that his signature was forged by use of a signature stamp.

Odd.

Each of the four doctors was required to contribute $100,000 towards a “cash reserve” in Keystone’s bank account. Hall argued that it was necessary to avoid paying checking fees, and that – eventually – there would be more money to distribute to everyone. Nick thought that he was paying for his ownership in Keystone.

COMMENT: Folks, if your bank requires hundreds of thousands of dollars to avoid fees, you really need to consider another bank.

There were questions about how the numbers were calculated and allocated among the doctors in Keystone, but Hall assured the doctors that the practice manager (Hall’s brother in law, by the way) had assured him everything was in order.

I feel better.

In 2007 two of the doctors left.

Later in 2007, Nick told Hall that he too was leaving.

In March, 2008 Hall gave Nick a hand-written sheet stating that Nick owed $151,769. Hall, being a good sport, said that he would offset the $110,000 that Nick had put into WACHN, but Nick had to transfer his interest to Hall. Hall would then – back to that good sport thing – “forgive” the remaining $40,769. Hall did not address removing Nick as a guarantor for WACHN’s debt, though.

Nick told Hall where to go.

Keystone issued Nick a 1099 for $159,577.

Hall said that Nick still owed $100,000 toward the Keystone cash reserves and $28,000 towards the WACHN buy-in. There was also a $38,010 bonus that Hall was paying Nick on the way out, being a good sport and all. Nick responded that he had paid everything he was supposed to pay, and – by the way – what bonus?

Sure enough, in 2011 the IRS swooped in on Nick.

Mission accomplished.

Turns out the $38,010 bonus was right. That however left a bogus $121,567 on the 1099.

Let’s fast forward through the rest.

Nick sued Hall and Keystone. There were several lawsuits, but we are concerned here with the tax-related lawsuit.

The Court decided that Keystone and Hall filed a fraudulent 1099 because of “spite arising out of the larger disputes between the parties.” Code Section 7434 allows for damages in this circumstance, and the Court gets to decide.

The Court awarded Nick damages of $178,954.

Our case this time was Angelopoulos v Keystone Orthopedic Specialists.

An Attorney, A CPA and Confidentiality

Do you have privacy protection if you tell me something as your CPA?

Your first thought might be yes, as your CPA might be the financial doppelganger to an attorney.

Then again, the answer might be no, as your CPA is not in fact an attorney – unless he/she is one of those rare birds that pairs-up a JD/CPA.

What got me thinking along these lines is the recent case US v Galloway.

Let’s travel to 2006. The IRS notifies Galloway that his 2003 return has been pulled for audit.

Audit starts.

In the middle of the audit Galloway’s CPA fires him. Why? Galloway did not pay his fees.

In 2008 Galloway gets sent to CID (Criminal Investigation Division), the part of the IRS that carries badges and guns.

As a heads-up: you NEVER want to deal with CID. It is one thing to argue with regular IRS, appeal penalties, stretch out a payment plan and so on. All that crowd wants is your money. CID investigates criminal conduct and they have a different goal: to put you in jail.

CID agents went to his business offices in Bakersfield, California. Upon their approach, a man in the office locked the door and called the police.

The CID agents also called the police and informed them there were two plain clothed and armed federal agents waiting for them to arrive.

The man stepped out of the building and provided them with the name of an attorney. The CID agents cleared out before the police arrived.

Nothing. Suspicious. There.

Since that visit went so well, CID next issued a summons for production of documents to the former CPA.

The CPA met with them, explained his relationship with Galloway and answered questions on how he prepared Galloway’s 2003 return. No great surprise: Galloway had forwarded QuickBooks information; the CPA asked a few questions, massaged a few numbers and produced a tax return. Happens in a thousand CPA offices every day.

There was a smidgeon of a problem, though.

Remember that the CPA had started the Galloway audit. As part of the audit, Galloway had provided him more paperwork, including additional and replacement QuickBooks runs. No big deal - usually.

What was unusual was that the new QuickBooks runs did not match-up to the earlier run the CPA used for the tax return.  

Galloway was charged with four counts of attempting to evade tax.

What to do?

Galloway sought to suppress all evidence obtained from his prior CPA. Why? Code Section 7609. The AICPA Code of Professional Conduct. Equitable authority. Applebee’s 2 for $20 menu.

You get it: kitchen sink. Galloway was throwing everything he had.

And this brings us to the Couch case from 1973. It was a Supreme Court case, so it is big-time precedent.

Couch owned a restaurant. At issue was unreported income. Cash. Pocket. Wink. You understand.

The IRS issued a subpoena to Couch’s accountant for books, records, bank statements, cancelled checks, deposit ticket copies, Sunday newspaper coupons and unexpired S&H green stamps.

Couch said: hold up. She had provided all that stuff to her accountant, so subpoenaing her accountant rather than her personally was nonetheless a violation of her Fifth Amendment right against self-incrimination.

I like her argument.

Ultimately – as Captain Picard would say – her argument was futile.

The Court was short and swift: Couch had no “legitimate expectation of privacy” upon providing information to a third-party with the goal of processing, straining and compressing that same information onto a government tax return.

Back to Galloway.

As you can see, he was taking a low-probability swing on a high-and-tight fastball.

He struck out. He could not make enough separation between his situation and Couch to avoid the precedent.

How do tax CPAs handle situations like Galloway in practice?

First of all: interaction with CID is rare. One can have a long career and never see the criminal side of the IRS.  

I have run into CID once or twice over 30+ years, most recently in connection with a fraudulent tax preparer in northern Kentucky. I also recently (enough) represented a client whose file was submitted by Exam to CID, but CID rejected the matter. The client was eye-rollingly negligent, but Exam hyperventilated (I thought then and now) and started seeing intent where only stupidity abounded.  

Anyway, here is what the CPA should recommend:

(1) Have the client hire an attorney

(2) Have the attorney hire the CPA

Under this arrangement, the CPA works for the attorney. He/she is protected under the attorney’s confidentiality privilege and cannot be compelled to testify unless the attorney releases him/her. The attorney will not – of course -  do any such thing.

This set-up is called a “Kovel,” by the way. Not surprisingly, it refers to a case by the same name.

What did Galloway’s accountant do wrong?

To be fair: nothing. Galloway was no longer a client. He was under no obligation to chase Galloway down.

Galloway really should have thought of that before stiffing the CPA for his fee.

Let’s however say Galloway was still a client. 

Folks, at the first hint or whiff of a criminal investigation I am (1) firing you or (2) you are providing me with a Kovel. Those are the only two options.

But it requires the accountant to recognize the danger signs.

Like a combined civil-criminal IRS examination, for example. Those are borderline unfair, as the IRS will pretend there is no criminal side to it. They introduce an unsettling miasma of entrapment, and they require the tax practitioner to realize that he/she is being played.

But that is not what happened with Galloway. CID went to his office, for goodness’ sake.

There was not a lot of subtlety there.