How do I report TurboTax Software Errors?

TurboTax Home and Business 2020 for Mac will not print.  It just locks up and I have to force quit.

When I try to efile my VA state return, it says I need to select a federal return to efile at the same time. I already efiled my federal, it was accepted and I received a refund. That is clear on the page it sends me back to to "select" a federal return. So I can't efile my VA state return. Software won't let me go forward.

error in turbotax ??  1040 sr line 11b subtracts from line 8b ok but capital loss carryover line 1 acts as tho the math is reversed changing the carry over #.   Looks like it started in 2018 premier & 2019

Please advise

TurboTax Deluxe 2020 does not correctly handle a Form 1099-R which represents an RMD from an inherited IRA that is not actually an RMD and was rolled over because of the CARES Act.

This is an image of my Form 1099-R Smart Worksheet. Please note that line 7 which is supposed to be a the value from line 1c says -4,342 instead of 0. This cascades an error through my federal form (by deducting too much from my income) and into my Illinois form, which TT20 finally caught in the error review phase.

Please dismiss my last post finally read the print & seen the error of my thinking

  Thanks

I erroneously input a non-taxable MO state refund (I took the standard deduction in 2019) of $1199 on lines A and C of the worksheet on MO-A which feeds line 9 on MO-A. I need to remove this error to correct my MO state refund for 2020. I tried to eliminate Form MO-A and that did not work. It did not eliminate the form. I need to eliminate the $1199 from lines A and C which feeds line 9 on MO-A. I tried to remove the input on the MO-A and could not. How can I remove these entries from MO-A?? 

There is an error on the worksheet for calculating late payment penalties for the state of Minnesota (MN).  The federal worksheet seemed to work without any problems (at least it didn't show that I owed a penalty).  (FYI, I paid all my quarterly payments on time for both the federal and state returns. Also, the amounts paid were such that I should not have been assessed a penalty.  I have small refunds on both returns and my estimated tax payments were equal for all 4 quarters for the state.)

The worksheet for MN assumes that the estimated tax payments made for Q1 and Q2, which were due 7/15/2020 for both the federal and state of MN, are applied as Q3 payments. This resulted in a small penalty on my tax return which not only was incorrect but prevented me from e-filing my state return. I decided not to file until I heard back from you. I was able to get around this problem by using 4/15/2020 and 6/15/2020 for the Q1 and Q2 payment dates respectively. Please let me know when this issue will be resolved. I do not know if this applies to other states as well.

Thanks in advance.

I am doing the Estimated Fed Taxes for next year.  Where do I record the Fed tax to be withheld from my monthly pension payment, plus that from my annual IRA RMD ??

I would like to report an error with TurboTax software. The problem exists in multiple versions (online Premier, and reproduced with paid pro Intuit software). Regarding Affordable Care Act forms (1095-A, box 1 and 2): If "marketplace identifier" is input wrong (for example switching with "policy number"), TurboTax does not catch the error. Final checks were completed without any errors caught! (Ready to file, CompleteCheck passed, all the way to payment stage.)

This is not a minor return error. The difference was thousands of dollars. (Note: When identifiers corrected, software seems accurate, as verified on paper by professional). Please correct this problem soon! At the very least, do not expect confidence in TurboTax (or our future use) if not corrected.

2020 Turbo Tax does not allow i(401)k employee contributions up to $26,000 for those age 50 and up. Instead, it enforces $19,500 for all ages. Last year, the software correctly allowed up to $25,000 for those age 50 and up.

I guess I will check back in a month or so to see if this has gotten fixed.