Olsen v Commissioner

You may recall that there is a”super” penalty that the IRS can assess if one understates his/her tax by too much. This penalty is not trivial: it is 20% and is called the accuracy-related penalty. In many cases the IRS assesses the penalty as a mathematical exercise. You can however request that the penalty be abated by providing a reasonable cause for doing so. A long illness or the death of a close family member, for example, has long been considered as reasonable cause.

We now have a new reasonable cause. I suspect that it will enter the tax lexicon as the “Geithner” defense, for the secretary of the Treasury under President Obama.

Here is what happened.

Kurt Olsen (KO)’s wife received interest income for 2007 from her mother’s estate. This means that she received a Schedule K-1, an unfamiliar form to the Olsens. KO normally prepared the tax returns, and he liked to use TurboTax. Upon receipt of the K-1, he upgraded his version of TurboTax as a precaution in handling this unfamiliar tax form.

TurboTax uses an interview process to obtain information. Using this process, KO entered the name and identification number of the estate. He also took a swing at entering the interest income, but something went wrong. The interest income did not show up on the return. KO was quite responsible and used the verification features in his upgraded software, but he did not discover the error.

The IRS did, though. They sent him a notice requesting an additional $9,297 in tax. The change in tax was large enough to trigger the “super” penalty of $1,859 ($9,297 times 20 percent).

KO knew he owed the tax, but he felt that the penalty was unfair. He felt strongly enough about the penalty that he pursued the issue all the way to the Tax Court. He represented himself under a special forum for small cases.

                Note: The tax term for representing yourself is “pro se.”

Now, the Tax Court has not been forthcoming in considering “tax software” as a reasonable cause. The Court has long expected one to use the software properly. In fact, a famous case (Bunney v Commissioner) has the Court stating that “tax preparation software is only as good as the information one inputs into it.”

The Court however took pains to distinguish KO, commenting that…

·         “We found petitioner to be forthright and credible.”

·         “It is clear that his mistake was isolated as he correctly reported the source of the income.”

·         “He did not repeat any similar error in preparing his tax return.”

·         “Petitioner acted reasonably in upgrading his tax preparation software to a more sophisticated version.”

The Court found reasonable cause to abate the penalty.

The key thing is that the taxpayer had an unusual source of income. He did not know where to look to check that the income had been properly included on his return. He did however meticulously follow the verification features in the software, and he relied – not unreasonably – on the software to report this transaction correctly.

This type of case unfortunately cannot be used as precedent. Tax Court Judge Armen also took care to cite the “unique facts and circumstances of this case.” Nonetheless, as more and more taxpayers use software to prepare their returns, it is expected that we will see more and more instances of the “Olsen” defense. 

Related Party and Tax Deductions

If you are a partnership, LLC or S corporation and report on the accrual basis, this may apply to you.

You may be aware that there are restrictions on deductions between related accrual-basis and cash-basis entities or individuals. These are the “related party” rules of IRC Section 267 and are well-known to tax accountants. By the way, these rules drive on a one-way street: the effect is to delay the deduction, not to delay the income.

                EXAMPLE ONE:

Sanctuary, Inc is a C Corporation and accrual-basis taxpayer. It owes $34,000 at year-end to Sam (a Schedule C) for the provision of goods or services. Sam is a 51% shareholder.  Sam is on the cash-basis, as most individuals are. Sanctuary, Inc cannot deduct the $34,000 until Sam includes it in income, because more-than-50% ownership triggers the related party rule.

                EXAMPLE TWO:

Sam (a Schedule C) owes Sanctuary, Inc $27,000 at year-end for the provision of goods or services.  Sam (a Schedule C) cannot deduct this until it makes payment. Sam (a Schedule C) is, after all, on the cash-basis. Sanctuary, Inc is quite unruffled by all this. As an accrual-basis entity, it will report the $27,000 in income without waiting for Sam’s (a Schedule C) deduction.

The trap here is the more-than-50 percent rule. The 50% requirement goes away if the transaction is between an S corporation, partnership/LLC and a shareholder or partner/member.

Change Sanctuary to a partnership, LLC or S corporation and the threshold drops to any ownership. As an example, an accrual to a 2-percent S- corporation shareholder would be disallowed under the related party rules.

Why? Here is how I make sense of it. As a pass-through investor, both sets of numbers will wind up on one income tax return. The IRS is therefore stricter than it would be if the numbers wound up on two tax returns, such as between a C corporation and an individual.