TurboTax 2025 is INCORRECTLY calculating taxable income in “What-If” form line 42

[FlyingCat]

Please fix the following problem I uncovered in TurboTax. Details below:

Version:           2025 TurboTax Home & Business

Platform:         Apple iMac M4

Filing Status:  Married Filing Jointly (MFJ)

Issue:              What-If Form, line 42 value needs to be equal to line 40 minus values in lines 41 a through e. However, What-If Form, columns (2), (3), and (4) are NOT subtracting line 41 from line 40. As result, value shown in line 42 is the same as value in line 40.

Interestingly, column (1), which TurboTax auto-fills with 2025 tax numbers, correctly shows value in line 42 as value of line 40 minus values of lines 41 a through e.

Please correct this What-If Form, line 42, columns (2), (3), and (4)  error.

[VolvoGirl]

I have Windows Home & Business program.

Do you have an amount on line 41e for the Senior Deduction?  If you have a high income you do not get the 6,000 or 12,000 subtracted.    I see the 12,000 shows up on my What-If in columns 2-4 but is not  subtracted because line 40 income is over the max. 

For Single the deduction starts to phase out at 75,000 and maxes out at 175,000
For Joint the deductions starts to phase out at 150,000 and maxes out at 250,000

[FlyingCat]

Yes, I have $6000 in line 41-e for the senior discount, but  line 42 is is not subtracting it from line 40, under columns (2), (3), and (4). It is only subtracting $6000 from line 40 in column (1).

[VolvoGirl]

Well how much is on line 40?  What filing status are you testing?  Single or Joint? 

[FlyingCat]

I tried to edit my reply above, but I was not able to.

My 2025 taxable income, filing as MFJ, is under $150,000. So the senior discount should apply.

[VolvoGirl · Accepted solution]

Yes I just tried putting in a lower income amount on 40 (I had a high amount before).  And it didn't subtract line 41.  So there is a problem.  

[FlyingCat]

Thank you for confirming my finding.

Will you be able to pass this information to the TurboTax team so they can fix this minor issue?

[AnnetteB6]

Thank you for sharing your experience with the What-If Worksheet.  We will submit this information to the development team for further investigation.  The first step in doing so is to provide them with a diagnostic tax file.  It would be helpful to have a diagnostic file from a user experiencing the issue.  

The diagnostic file will not contain personally identifiable information, only numbers related to your tax forms.  

If you would like to provide us with the diagnostic file, follow the instructions below and post the token number in a follow-up thread.  

For a Mac desktop version of TurboTax, use these steps:

• Select Help at the top of the screen.
• Select Send Tax File to Agent.
• Post the token number here.

@FlyingCat 

[martinb0820]

I'm experiencing the same issue with TurboTax 2025 on Windows 11.

To be clear - this anomaly shows up when column 1 is simply copied to column 2. "Use 2026 tax rates" is NOT checked. So columns 1 and 2 should be identical.

The (hopefully) temporary fix is to override the value in column 2 with the correctly calculated value in column 1.

Although the ultimate goal is to do what-if calculations with the 2026 tax rates, I haven't looked into whether any differences between 2025 and 2026 tax rules would invalidate this temporary fix.

[FlyingCat]

A simple short-term solution I am using to bypass this software bug, is to enter the sum from rows 41-a through 41-e into row 35 "Other Deductions"; this way, the value shown in row 42 will take into account the subtraction of values in rows 41a-e.

[SharonD007]

Thank you for bringing the What If Worksheet calculation you experienced to our attention.

We take reports like this very seriously. Our technical team thoroughly investigated the experience that you reported by testing the calculations on the What If Worksheet in Windows and Mac. However, we could not reproduce the issue on our end. If you provide a diagnostic file, we can test what you experienced.

We appreciate your patience and your help in improving our product.

[martinb0820]

The issue is apparently resolved now. I'm not sure which automatic update fixed it, but the issue is no longer being observed.