2024 Standard Edition - Schedule 15 - Cannot defer entire FSHA contribution deduction to a future year

[755598729]

Why is the Schedule 15 "If you wish to claim less than the maximum amount, enter it here." field value of $0.00 not reflected in box 43 of the same schedule?

Furthermore, why is this the only field on the schedule that does NOT have a number assigned to it?

[TurboTaxSusan]

You can override line 43 to claim $0 for your FHSA deduction. You will still be able to NETFILE with the override.

The line for "If you wish to claim less than the maximum amount, enter it here." is only in TurboTax which is why it has no number.

[755598729]

Hi Susan,

Thanks for your prompt response!

While I do recognize the fact that this field can be overridden, the only reason as to why this would be necessary would to address a fault within the software.  The response I was expecting -- but clearly have not received -- is one that:  (a) acknowledges the fault; and (b) provides a commitment to issuing a "fix" in a timely fashion.

Regarding your position stating that the ability to NETFILE will be preserved, despite applying an override to this field, your own software claims otherwise...i.e. "NOTE:  If you override this calculation, you cannot file this return using NETFILE."  So, with all due respect, either you or your software is mistaken; as a user, I cannot determine which.

As previously stated, a simply fix -- and spending my entire career in IT, I can assure you that this is indeed a very simply fix -- would resolve this issue without any need for manual intervention or the possibility of jeopardizing the ability to NETFILE a return.

Please advise...thx!

[Rick889]

I agree with the user this is a software bug and requires an urgent fix and a software update. 

When I enter 0 in the line "If you wish to claim less than the maximum amount above, enter it here....."

We should get 0 deduction for 2024.   It's incorrectly calulated.

PLEASE fix this soon.

[TurboTaxAniqua]

@755598729 We are aware of this issue, and our development team is working on a resolution. Once it is resolved, we will update you in this thread. We appreciate your patience.