Skip to main content
Level 2
December 7, 2019
Solved

There appears to be an error in the QBI calculation as it relates to vehicles w/input for actual expenses, listed as UBIA, but not being included in the calc. please call

  • December 7, 2019
  • 2 replies
  • 26 views

(NOTE:  This issue has been submitted to Technical Support)

Client has a Schedule C with over $100K of net income and QBI.  NO wages in the Schedule C.

Overall, the client has about $700K of taxable income, but no other QBI related income.  Thus due to no wages, the client should get 2.5% of UBIA.

Client has only ONE asset.  A vehicle, used greater than 50%, and utilizing the actual expense method, so taxpayer is getting some depreciation.  The UBIA of this one asset is being calculated properly AND has a worksheet indicating that the asset does qualify as an asset for UBIA.

The problem is that the QBI calculation does NOT include this in calculating the deduction.  After analyzing, we determined that if there were NO "actual expenses" input (in the depreciation input area - ie for gas, repairs, etc) then the program does pick up the qualified asset for the calculation.  But put in $1 dollar for any expense, the program does NOT included UBIA for the calculation, even thought it still indicates that the asset IS a qualified asset for UBIA!

We believe there is a programming error, but please let us know either way.  We are also happy to provide the client copy to Lacerte for their review.

This topic has been closed for replies.
Best answer by abctax55

This is NOT Intuit/Lacerte support.  You will need to contact them directly to report the possible defect.

This is a peer-to-peer forum of fellow users of the software.

I believe Ctrl L starts a report directly to Lacerte concerning a perceived programming error.

I haven't seen this one reported yet, and haven't run across the scenario you describe on a client (yet).

2 replies

abctax55
abctax55Answer
Level 15
December 7, 2019

This is NOT Intuit/Lacerte support.  You will need to contact them directly to report the possible defect.

This is a peer-to-peer forum of fellow users of the software.

I believe Ctrl L starts a report directly to Lacerte concerning a perceived programming error.

I haven't seen this one reported yet, and haven't run across the scenario you describe on a client (yet).

HumanKind... Be Both
sjrcpa
Level 15
December 7, 2019
@abctax55  Couldn't stay away? :smile: Welcome back.
The more I know the more I don’t know.
abctax55
Level 15
December 7, 2019

Jon...sorry to have hijacked your serious post. I see you edited, and have reported the problem to the PTB.  Thanks!

HumanKind... Be Both
jon-aAuthor
Level 2
December 7, 2019
No problem... I appreciate the guidance on reporting directly to Lacerte:  Control "L" was correct! :)