I am being asked to correct an entry for "previously disallowed QBI losses to be reported as separate business".... I don't know that that means or how to correct it.

[bobpierce1]

I am having the exact same problem.  I have entered every single number from the K-1 including the 199A, and this one issue is preventing me from filing.  Is this a calculation error in the TurboTax software?  How do I go about confirming what the problem is?

[xtinaissharp]

I'm having the same problem! I've seen a few threads about QBI issues in general and people not being able to e-file. It seems like the Turbotax has been waiting on the IRS for a specific form... which according to Turbotax specialists was supposed to be good to go on 2/20.

I finally checked again today (2/21) to FINALLY file, and I run into the same annoying loop. I click continue, and then they won't let me e-file unless I "correct" the issue. The kicker is I don't have anything regarding a previously disallowed QBI on the K1 forms my accountant gave me so... Turbotax, what's up?

[xtinaissharp]

I figured out a way to bypass/get past the QBI review issue. Maybe it will work for you.

In the "Describe Your Partnership" section when you edit your K-1, there are 5 checkboxes. By default the "All of my investment in the activity is at risk" is checked. Originally I unchecked it, but after refilling out this section I left it checked and had no issues. I was able to file this morning.

Hope this helps you! 

[bobpierce1]

@xtinaissharp @he42 

Tina is in fact very sharp! 🙂  I checked the box you recommended, and it worked!  I don't know how many combinations of those boxes I went through before posting to the board, but I took your advice this morning and was able to file.  Thanks for sharing your advice with us.  It is greatly appreciated.  All the best to you, and thank you, again, for your assistance with this.

[YingShah]

I checked "All of my investment in the activity is at risk", unchecked "I have at-risk losses carrying over from 2018", then click continue, but "I have at-risk losses carrying over from 2018" is still checked automatically.

What is the problem?

[jsutsomeguy]

I had to remove the K1 and start over.

[belkys1234]

I am having the same problem for 3 days I been trying to efile my return and I get the same error, is there any way I can opt out of this error I never had a lost on my k1 and I just want to efile my return.

[belkys1234]

I am going to try that, in case it does not work is there a phone to call turbo tax for help?

[bobpierce1]

Belkys1234, I completely deleted the K-1 and started over, and I ran into the same problem.  I tried to find a customer support phone line and couldn't.  I was in the same boat and becoming very frustrated until @xtinaissharp posted the tip about checking the box for investment being at risk.  That fixed it for me.  I've never had a loss either, but noting that the investment is at-risk eliminated the hurdle in the review stage that was preventing me from e-filing.  Hope it works for you!

[misterexact94]

Yo! Tina!! Someone should be paying you for this advice, it worked for me after 2+ hours of losing my freaking mind trying to figure this out. Anyone who is having this problem, this should be the easy fix and keep your numbers the same. UGH!!! THANK YOU!! 

[HYTahtinen]

Tina is right! Exact same scenario. It worked!

"In the "Describe Your Partnership" section when you edit your K-1, there are 5 checkboxes. By default the "All of my investment in the activity is at risk" is checked. Originally I unchecked it, but after refilling out this section I left it checked and had no issues."

[xtinaissharp]

@misterexact94   So many other message boards got me nowhere so I'm happy I was able to help most of you!😊

[rrmills7777]

But what if this isn't true?  My investment isn't "at risk", and checking that box actually decreases my tax liability, which can't be right.  I'm not willing to do that to work around a TurboTax bug.  Any other suggestions?

[MarkM1]

I agree.  I don't want to file a return with false information to get past this technical bug.