Sales tax calculation for Major Purchases is in error?

[Richardowens55]

The decimal point is in the wrong place

[wdcrater]

You are 100% correct.  I wonder when they will fix it?

[busyman00]

I'm getting a similar error, but it looks like more than a decimal place.  I entered two vehicle purchases with sales taxes of about $6,000 but the "larger" amount checkbox shows $93,338 which is more than the two cars and their sales taxes combined.  Since I didn't enter any other items, I don't know where it's getting this number.

[DaveF1006]

This may be the purchase price for the two vehicles purchased. Go back to the section where you made the entries and carefully check your answers to see if they are correct.

[user17697295673]

The calculation is incorrect.  My sales tax rate in Florida is 6.5%.  The turbo tax sales tax calculation uses purchase price multiplied by .065%.  This is incorrect, should be purchase price multiplied by .065. See an example.

Purchase price is $10,000.  Sales tax at .065% =0.00065 x 10,000 v $65.00.   10,0000 x .0065 =650 $650 which  is correct..

Hope this better explains it.

[RogerD1]

It sounds like you are taking sales taxes for large purchases as a deduction - if so, the amount of sales tax paid on the large purchase is not calculated by TurboTax, but must be entered by the user.  The IRS also has a sales tax calculator here  IRS Sales tax calculator .  It hasn't been updated for 2025 yet, but I used data of $100,000 income for a single individual in Miami FL and it came up with a sales tax deduction of $1054, which is similar to a result that I got for TurboTax 2025.

If you could provide more information about where you are seeing that error (such as what screens you are on), that would be helpful in diagnosing the issue.

[babbleablea]

yes, but turbotax chooses to "allow" the major purchase deduction based on the sales tax. 

I am denied my major purchase sales tax deduction, even though the tax rate matches the local tax rate.  Contacted TT today, the helper saw that it was correct, saw the error, and could do nothing to fix it. Ok, they were not a programmer - but they also seemed to dismiss it as a me problem rather than submit a ticket for the error.

FIX THIS BUG