Why sign in to the Community?

  • Submit a question
  • Check your notifications
Sign in to the Community or Sign in to TurboTax and start working on your taxes
Level 1
posted May 31, 2019 6:00:38 PM

The family HSA contribution limit for 2016 is the 2015 amount. It should be 2015 +$100

0 8 1262
1 Best answer
Level 15
May 31, 2019 6:00:42 PM

I've confirmed that the current version of 2016 TurboTax is still using $6,650 for the family limit instead of $6,750.  I'll notify the moderators so that they can pass it along to the developers.

8 Replies
Level 15
May 31, 2019 6:00:39 PM

Are you using the 2016 software?

Level 15
May 31, 2019 6:00:42 PM

I've confirmed that the current version of 2016 TurboTax is still using $6,650 for the family limit instead of $6,750.  I'll notify the moderators so that they can pass it along to the developers.

New Member
May 31, 2019 6:00:43 PM

The government hasn't released all of the forms and calculations for this coming tax season. Until they finalize everything, the product will show the 2015 forms and calculations. We release the product this early to allow customers the opportunity to get a head start on their personal information portions of the product.

Level 15
May 31, 2019 6:00:45 PM

For those who are using the CD/download version of TurboTax (which is probably everyone who has noticed the discrepancy in the HSA limit for family coverage at this point), you can use forms mode to override the erroneous limit until the value is corrected by TurboTax developers.

New Member
May 31, 2019 6:00:48 PM

Fair enough.  As long as I didn't really overdeposit by $100.  That kind of TT alert is scary.

Level 15
May 31, 2019 6:00:50 PM

Update your copy of the CD/download version of TurboTax, this bug was fixed in December.

New Member
May 31, 2019 6:00:52 PM

Any idea when it be fixed in the online version of TurboTax? It's still showing an erroneous $100 excess contribution from my employer.

Level 15
May 31, 2019 6:00:54 PM

This was fixed in the online version in December as well.  I just now verified that it is still working correctly.

Airchon, I suggest posting a new question regarding your situation since the cause is not the result of the bug, now fixed, originally reported in this thread.