nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

One step update changing tax planner results

Ben12

After update R64.29 fixable errors have popped up in tax planner. After using the one step update, projections for taxable social security income are incorrect in tax planner. This is corrected by going to Bill and Income Reminders for Social Security Income and choosing Edit this instance and all future instances and choosing Done (make no changes). After doing an update in Investing the results in tax planner results are correct.

Find more posts tagged with

Tax Planner

Comments

markus1957

I'm seeing similar behavior. It seems reminders that have splits are getting jumbled and/or corrupted by the OSU process. Quicken is still not yet convinced an issue exists but given the number of similar posts that describe issues with reminders, it should get recognized soon.

Jim_Harman

@markus1957 When you say "jumbled" do you mean the order of the split lines is changed, split lines are lost, or what?

From other discussions, it seems that changing of the order of the split lines is associated with mobile Sync being turned on. Those who have complained about that say it stops if they turn Sync off.

Bill3

After R64.29 I noticed missing withholding records in the tax planner, and that correcting them did not save. Validation of the data file allowed me to save my corrections again.

markus1957

Jumbled as in the amounts stay in the same order but the categories get changed. But more often, I see it in Tax Planner when amounts don't add up or scheduled gets changed to projected based on YTD. When I see the condition, if I run a super-validate, it shows the affected reminders were "corrected".

Deleting and re-creating the reminders does not help, nor does a template copy. It's related to OSU and seems to happen whether Sync is On or Off. It only impacts reminders with splits. For me it's social security payments because of the multiple lines required to track it.

h stansfield

I'm glad I'm not the only one. For me, tax planner suddenly doesn't (a) stay on "scheduled bills and deposits" and (b) doesn't even see future IRA withdrawals as income. Currently I see virtually zero value in the tax planner. It went from projecting a small refund for 2025 to telling me I will owe a massive tax.

I'm looking for another tax planner tool that I can actually put data in and have it do a decent projection. Oh, Quicken still doesn't recognize the new over-65 standard deduction amount that Congress recently created.

markus1957

I cannot break reminders with splits as of yesterday. I waited until this morning after a new day's OSU to see if the reminders remained uncorrupted and they did.

I cannot pin down exactly what happened but have a couple of candidates. I went from reliably being able to break the reminder after OSU as verified by seeing changed values and anomalous behavior in tax planner and also "corrected scheduled reminders" in super-validate reports to not being able to break it.

Three things I did but really cannot pin down if any one of them are responsible.

First, I deleted QW.rmd, a legacy file from BillMinder that is still used somehow in Quicken and which has been implicated in the past for bad behavior in reminders. I had not looked at it in a while and it was rather large. It's now only about 40 kb.

Second, I reset the cloud file after a super-validate and then made no accounts selected for mobile sync.

Third, after a super-validate, I would always go back to the problem reminder(s) and check them to see if anything changed. I would then resave them. The next OSU would result in corruption, sometimes even before the next OSU, I'd notice Tax Planner shift from using scheduled reminders to YTD use to date. After the last 2x super-validate, to verify a clean file, I performed OSU immediately and Tax Planner values remain as expected.

Some form of corruption was being spawned using Quicken and being perpetuated by the OSU process. It seems for now, one of the steps I took (or a back-end change in the OSU process) corrected the corruption and the file is now behaving as expected. Several others are reporting this type of issue with reminders containing splits. Hopefully, thru trial and error, a specific set of steps that can be taken to restore the file will be identified.

Ben12

This issue seems to have fixed itself this morning. Not sure what changes happened in the mothership.

Ben12

false alarm, problem returned this morning