Skip to main content
Chessie
Level 4
February 12, 2026
New

Hidden worksheet computing SE health insurance premium deduction miscalculating when have Exchange insurance, a small repaymnet of adv PTC, and supplemental vision & dental premiums

Related products:ProSeries
  • February 12, 2026
  • 2 replies
  • 15 views

ProSeries has a hidden worksheet as the go-between between  Form 8962, Part II repayment of excess PTC and Form 7206 SE Health Insurance Deduction.  At the bottom of Form 7206 there is a statement "A self-employed health insurance adjustment of $____ from premiums paid through an exchange is included as an adjustment to income but does not appear on these worksheets."

I want to have access to that hidden worksheet and see that computation because it appears to be wrong! 

Here's an example.  If Sch C has say $40K net for 12 months activity. Form 1095-A Part II Column A minus Column C is $3,300 premiums paid while Form 8962 shows a repayment of excess advanced PTC of $750.  Also the taxpayer paid an additional $320 in premiums for vision & dental.  The self-employed health deduction on Schedule 1 line 17 should be $4,370  ($3,300 + $750 + $320).

However, that worksheet is instead reporting a lower amount on Schedule 1 line 17 and throwing the balance on Schedule A medical when there is clearly sufficient Schedule C income and no losses from any other source.

I tested this at length with a Schedule C and self-employed health premiums.  If I only have Exchange insurance with repayment of excess adv PTC, it computes correctly.  If I only have non-exchange premiums, it computes correctly.  But a combination of exchange premiums plus repayment of excess adv PTC plus non-exchange premiums results in an error.

I also would like ProSeries coders to re-visit the computation on that worksheet because it should deduct the entire amount.

2 replies

Level 15
February 12, 2026

I don't think ProSeries uses a worksheet; I think it still uses the 'math' from the Iterative Calculation from Revenue Procedure 2014-41.

The Iterative Calculation goes back and forth until it comes up with an answer within $1 difference.  However, sometimes (fairly often) the math doesn't work out cleanly (the results never get within $1), so then the Alternative Calculation is used, which effectively stops the Iterative Calculation after a few back-and-forths.

When using the IRS Alternative Calculation, the math doesn't completely work out so there is a missing amount that doesn't fit into the credit or the SEHI deduction.  ProSeries puts the missing amount on Schedule A.

Option #1:  Have the taxpayer consider a small, deductible Traditional IRA contribution.  That can sometimes do multiple things: (1) get the deduction. (2) lower MAGI to increase the Premium Tax Credit, and (3) sometimes jiggle the math enough so that the Iterative Calculation works out and it doesn't need to resort to the Alternative Calculation.

Option #2:  The IRS also says that other reasonable methods can be done.  You could 'jiggle' things a bit by testing out putting small amounts of that missing amount (the amount that went to Schedule A) and put it on the Schedule C spot for health insurance, then check to see how the number come out.  It usually takes several back-and-forths of testing and checking, but you can usually get it pretty close.

Option #3:  If the amount going to Schedule A is small, just accept it because it is how the Alternative Calculation from Revenue Procedure 2014-41 works.

Chessie
ChessieAuthor
Level 4
February 12, 2026

Yes, I was hoping it could show me the math that it arrived at as the final number in the Iterative Calculation from Rev Proc 2014-41 or the Alternative Calculation.  I've just never had it be off more than a few dollars in the past.  This one is off a fairly substantial amount for this client which didn't make sense.

Yes, the client has already made their full 2025 IRA deduction - I've used that trick many times.

Intuit's CSR told me to just override the health insurance deduction!  Uh... Nope!

Your Option #2 is what I had decided to do after retiring last evening if no coding fix or other alternative presented itself today.

Thank you so much for your helpful post and suggestions!  Blessings on your day!