TurboTax NOT considering IRS disaster extension for 2023 storm impacted area?

[titi10402022]

AFAIK, IRS does the following extension for CA residents who live in the impacted areas by the 2023/01 storm.

2022Q4 1040-ES: from 01/17/2023 to 10/16/2023.

2022 1040: from 04/18/2023 to 10/16/2023.

2023Q1, Q2, Q3 1040-ES: from 4/18, 7/15, 9/15 to 10/16/2023.

Does TurboTax consider these extensions for the resident living in these area? It seems to me at least 2022Q4 1040-ES extension is not considered?

My situation is I paid $X for 2022Q4 1040-ES on 01/17/2023, and then $Y for 2022Q4 1040-ES on 10/01/2023 again. When I file my 1040, in TurboTax I add $X+$Y as 2022Q4 1040-ES, with payment date 10/01/2023 (TT doesn't allow input multiple 1040-ES entries for one quarter, so I pick the latest). The tax penalty is much higher than when I change the payment date to 01/17/2023.

I look at the TT generated 2210 and its instruction. It seems TurboTax doesn't consider the extension. Is there a way to notify TT about this for adjustment? Or, can I just use 01/17/2023 as the payment date?

Thanks!

[fanfare]

When you file your 2023 tax return, if you paid before Oct 16th, use April 15th, if necessary, as the payment date for your first quarter 2023 payment because you paid on time. any excess will be applied to the second and third paymentsw.

Top up now to complete expected 2nd and 3rd payments on time.

" It seems to me at least 2022Q4 1040-ES extension is not considered?"

This is the last payment for 2022 taxes. I don't think IRS extended the deadline for this payment.

The disaster hit later.

@titi10402022 

[Update:  IRS extended the deadline for this payment, also.]

[dmertz]

Enter $X+$Y as paid on 01/17/2023, not 10/01/2023.  Because you are in an affected disaster area, the 10/01/2023 payment is treated as having been paid on 01/17/2023.

[titi10402022]

No, IRS does extend 2022Q4 1040-ES from 01/17/2023 to 10/16/2023. I think the storm happened early Jan 2023.

[titi10402022]

Thanks for the suggestion. I thought TT should have been able to handle this automatically, or at least give some hints on this issue. :(