Turbotax 2020 has a bug entering the SSN for alimony recipient. The SSN field deletes the leading "0" of SSN and barf saying invalid SSN. The SSN field is designed wrong.

[ravisundar]

Whomever wrote the software for Turbotax 2020 version, this person is totally incompetent and uses wrong format for the information to be entered in SSN field. That is why it skips the leading "0" in SSN field.

[PattiF]

There is a known issue with this. In order to be able to properly record the alimony for both parties sake, there will be a solution to this problem. Some TurboTax customers were experiencing an issue when entering in the social security numbers that begin with a 0 when entering alimony paid in the TurboTax desktop version of the program.

If you're experiencing the issue above,  please go here to receive email notifications when any updates related to this issue become available.

[ravisundar]

The new update from Turbotax seems to have fixed this bug. After recent update, when I checked the alimony deduction section, the leading "0" automatically appeared under recipient's SSN field even though the earlier version deleted the leading "0". I didn't have to retype the SSN in the SSN field at all. I have successfully filed both returns (Federal & State).

Ravi.

[LeedsRG]

I downloaded the most recent update today (2/18) and I'm still having the same problem.  Did you just do the normal update or something different?  Thanks...

[ravisundar]

I did the normal update that Turbotax 2020 prompts you when you open the desktop app every time if there is an update. After the update, I didn't have to retype the recipient's SSN again. When I looked at the SSN field, it already had the leading "0" without the need to retype. In other words, whatever SSN I entered earlier with leading "0", it appeared automatically after the update.

Ravi.

[LeedsRG]

Thanks Ravi   Are you using on-line version or the CD?  I'm using the CD and have heard the updates are later there compared to on-line.

[ravisundar]

I always use downloadable version because the CDROM drive in my desktop PC has a problem. Also, it takes a very long time to install from CDROM because of data transfer speed CDROM vs binary file from hard drive.

Ravi.

[LeedsRG]

thanks.  I think the CD updates are behind so I'll wait on the update that fixes this.