What to Do If Already Contributed to HSA but Not Eligible?

Check eligibility on the go — browse 7,000+ HSA-eligible products in the free app.

What to do after learning you’re ineligible

Contributing to a Health Savings Account (HSA) is a great way to save for medical expenses while enjoying tax benefits. However, it's essential to ensure you are eligible to contribute to an HSA to avoid any penalties or tax implications. If you have already contributed to an HSA but later found out you are not eligible, don't worry, there are steps you can take to rectify the situation.

Here are some steps to follow if you find yourself in this predicament:

Why acting quickly and checking eligibility matters

• Stop making further contributions: Once you realize you are not eligible to contribute to an HSA, the first step is to stop making any additional contributions.
• Contact your HSA administrator: Reach out to your HSA administrator to discuss the next steps and inform them of your ineligibility.
• Correct excess contributions: If you have over-contributed to your HSA, you will need to correct this mistake to avoid penalties. You can do this by withdrawing the excess amount before the tax filing deadline.
• Pay applicable taxes: In case you have already contributed more than the allowed limit, you may need to pay taxes on the excess amount. Consult with a tax professional to understand the implications and process.
• File the necessary forms: You may need to complete and submit IRS Form 5329 to report the excess contributions and any applicable taxes.

It's crucial to act swiftly and address any HSA eligibility issues to avoid potential penalties and ensure compliance with IRS regulations. Always consult with a financial advisor or tax professional for personalized guidance based on your specific situation.

It's important to regularly check your eligibility for a Health Savings Account (HSA), especially before making contributions. If you mistakenly contributed to your HSA despite being ineligible, you can take some straightforward steps to correct this issue.