Form 2210 had asked for 4 withholding periods, but it was updated for only 3. The fourth value is locked in and causing errors.

[dhattrupbiz]

Turbotax online did not have form 2210 until Feb 26, but it had asked for all the questions.  The final questions does not match what it originally asked.  The data in the backend is now out of sync with the user input values and creates issues.  I need to clear out the back end values.

[dhattrupbiz]

Prior to 2/26, TurboTax Online supported the Q&A questions for Form 2210.  When entering actual withholding, there were four periods shown (although there were some date issues in those periods).  Assuming it would be the same as prior years, I had entered withholding for dates ending 4/15, 6/15, 9/15, and 12/31.  After the update, the form changed to only three periods ending on 7/15, 9/15, and 12/31.  When I reset the numbers, TurboTax complains that the numbers don't add up to the total withholding.  It appears the Line D validation is still adding in the OLD 6/15 value.  The three values in Line D show the NEW 7/15, OLD 6/15, and NEW 9/15.  The lines in Section A show the NEW 7/15, NEW 9/15, and NEW 12/31.  If I play with the numbers so that both Line D and Section A independently add to the correct amount, Turbotax still complains, leading me to believe the OLD 6/15 value is getting added to Line D along with all three new values.  This needs to get fixed ASAP, as TurboTax refuses to e-file when it believes there are issues.  I have already paid my fees, so TurboTax online does not even give me an option to clear data and start over.

[dhattrupbiz · Accepted solution]

Finally found a feature in Tools where one can delete form 2210.  This effectively wiped out all the data and allowed me to reenter the information properly and now Turbotax stopped complaining.

This was not an intuitive way to solve the problem, and I was lucky that I stumbled on the form deletion option as I had no idea it existed.

[JHolroyd]

Thank you!!! Also encountered this issue. TURBOTAX please fix this! A very frustrating issue I have wasted hours trying to fix.