I changed the next instance of an estimated taxes reminder from $3,700 to $0. In the Bill and Income Reminders:
In the Tax Planner:
Hello @Chris_QPW,
I was able to replicate this issue and forwarded it to the proper channels to be further investigated. I can see that you already submitted logs for this issue.
While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.
We apologize for any inconvenience!
Thank you.
(CTP-11835)
Thank you @Quicken Kristina !
I have noticed this issue many times over many years. It happens every time when making a change to the next instance of a recurring Reminder. It is not a hit-or-miss random issue.
If I then decide to keep the edited instance and enter it into the account register, then the change will be properly captured in Tax Planner.
BTW, the edited next instance of the Recurring Reminder will be properly reflected in account registers when they are set to show Reminders.
I know I reported this issue many years ago but haven't followed up on it since then. For me it is usually only an issue from mid-Dec through mid-Feb when finalizing plans for end of year taxes, IRA distributions and Roth IRA Conversions which is then followed by budgetary planning for the next year and then followed by tax returns. By the time I get through all of this I tend to forget about this issue until the next Dec when that planning and reporting process starts all over, again.
Thank you for your reply and the additional information,
I observed the same behavior when I replicated the issue in my Quicken. I noticed this happens with recurring reminders only. When I created a one-time reminder and updated it, the new amount updated in the Tax Planner.
Thank you!
When I created a one-time reminder and updated it, the new amount updated in the Tax Planner.
I, too, have noticed this issue only happens with recurring Reminders, not one-time reminders.
Hi @Boatnmaniac and @Chris_QPW, is this issue still happening?
Yes, the problem is still there.
I agree. The issue has not been resolved.
This issue is still not resolved in R65.29. If you have a Reminder that is set to Remind me, not Auto accept, and you enter or skip an upcoming Reminder, the Tax Planner handles it correctly. But if you edit the next instance, it uses the ongoing Reminder amount, not the edited amount for the next instance.
This is not a recalculation issue; it continues after restarting Quicken.
Steps to replicate:
This affects me because I have several taxable dividends that are paid on different dates near the end of the year. I have a Reminder set for the total estimated amount of the dividends. When I have received and entered some but not all of the dividends, I adjust the December Reminder to reflect the portion I have received. The Tax Planner uses the full estimated amount plus the amounts received from previous instances of the Reminder, which is wrong.
Hello All,
Thank you for confirming that the issue is still ongoing.
Our team has requested that you please submit a sanitized data file via Help > Report a Problem so it can be added to the ticket and help with the investigation.
Once you’ve submitted it, please let us know so we can get it attached to the ticket.
Thank you!(CTP-11835)
Report a Problem with sanitized file sent.
Great, thank you!
This issue applies to any tax-related reminder where the next instance has been edited to change the dollar amount and/or the transaction date. I've noticed this many times over the years with IRA distributions, Roth IRA conversions, property tax bills, healthcare expense bills and charitable contributions.
It makes year-end tax planning more difficult because in order to get any changes to dollars and/or dates reflected in Tax Planner so the effect of those changes can be observed one needs to change the entire Reminder, not just the next instance. And when done one needs to remember to return the Reminder for future dates to the original dollar amount and/or date.
It should be noted that this issue exists only when the next instance has been edited but not yet entered. Once the edited next instance is entered into the register then it is properly captured by Tax Planner.
@Boatnmaniac Thank you for the additional clarification and examples. That distinction is very helpful.
