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; } } }

Edit Current Paycheck - Add New Tax Item does not work

Wayne.royal

Quicken Premier R38.29
Using Edit Current Paycheck feature I am unable to "Add New Tax Item"

This is a drop-down button that should allow adding a new item, but when I click on the button, it only changes color and does not show the options to add a new item.

Find more posts tagged with

Comments

gmherteg

Same issue as other post with a bug report filed: https://community.quicken.com/discussion/7907319/cant-add-tax-item-to-paycheck

ctitus59

Same issue with R38.29. "Add Pre-Tax Deduction" and "Add Post-Tax Deduction" buttons works as expected, but not the "Add Tax Item" button. Same problem exists both inside the Track Paycheck setup and when editing a paycheck inside the ledger.

Dreamer3D61

Ok this seems to be another ongoing problem with Quicken! I wanted to setup my paycheck and everything was fine until I went to add one more item to the TAX section. No matter what I do I am unable to add a tax item to that area of the paycheck setup. When I go with Quicken support on chat the agent suggested I call a number the next day so that they could to a "Remote connection" in order to figure out what is going on. EXCUSE ME! I am not allowing them to remotely explore around in my computer to figure out what is wrong when I've discovered so many other users are having the same issue!

[Removed - Rant]

Quicken Anja

Hello All,

Thank you for taking the time to report this issue to the Community, although we apologize for any frustration or inconvenience experienced.

This issue is a bug that has been reported to our Development and Product teams for further investigation and resolution, though we do not have an ETA at this time.

Once a solution is created it will be made available as part of a future release.

Thank you!
(QWIN-20414/CTP-3480)

Dreamer3D61

[Removed - Off Topic/Disruptive]

James McAfee

We are now 3 weeks out from the initial complaint of this bug. Please get this fixed. Thank you.

jr_ece

I just used this feature in the Dec/Jan time frame, but like others have reported it is now broken.

@Quicken Anja Is there an ETA now that a month has gone by? This one feature is preventing paycheck entries until resolved. Seems this should be a high priority and fast track release. Thanks!

Chris_QPW

jr_ece said:

I just used this feature in the Dec/Jan time frame, but like others have reported it is now broken.

@Quicken Anja Is there an ETA now that a month has gone by? This one feature is preventing paycheck entries until resolved. Seems this should be a high priority and fast track release. Thanks!

There is never an ETA on any bug.

jr_ece

> @Chris_QPW said:
> There is never an ETA on any bug.

My apologies. Her response on 2/8 implied there would be an ETA at some point. The phrase in reference is "...we do not have an ETA at this time.".

Also, for those who mentioned versions with this bug I can confirm it also exists in R38.30.

Chris_QPW

Yes, I agree it sounds like that, but I have been on these forums since 2006 and have yet to ever see an actual ETA posted for any bug, or for the matter a feature. Other than maybe something like "soon".

They just aren't going to commit to a timeframe that they might miss or even to fixing a given bug.

@Quicken Anja maybe dropping the "at this time" might be appropriate, because we both know by the time you will know the "timeframe" it is because they have just released it in patch.

jr_ece

@Chris_QPW Appreciate your perspective and unfortunately agree. I've been a "member" for a long time (don't recall when, had to start over with separation from Intuit), but I've not been very active due to what you've described and deletions (too transparent??). I guess I had some kind of fleeting hope for a moment

.

I really am hoping this one is a top priority as I am stuck with no paycheck entries back into December after discovering several were broken and removed them (different thread on paycheck damage from possible mobile sync).

Chris_QPW

@jr_ece as it turns out they just announce a new version that is supposed to fix this problem:
https://community.quicken.com/discussion/comment/20251553/#Comment_20251553

How is that as an example of what I meant about an ETA?

But it is in "staged release mode" and already paused (I didn't get it this morning). And it seems the manual patch for it isn't out yet.

jr_ece

I was just over there looking at patches and found the R39.17 Mondo. I came back here to post results but you beat me to it!

I just installed and things went from bad to worse. First, the old problem is not resolved with R39.17. Still can't add new tax item.

Now for the really bad. I don't know if my new problem was already present from another recent update and I didn't realize it, or if R39.17 introduced this new HUGE problem. Every paycheck back to 5/12/2006 (things appear fine from that point back to 7/28/2000) has been modified to be identical to the latest paycheck. Whoa. This means a LOT of fouled transactions to resolve. I have a 3/9 backup prior to installing R39.17 but it has the same issue when restoring from within R39.17. I believe I need to rollback to see if the issue is with R39.17 or if I've had it for a few months and didn't know it. I did some annual income mapping sometime in the last 5 or 6 months so I think it has to be relatively recent. The issue I have is the entry of MANY transactions in that time frame if I need to go back to an old backup. The other issue with that could be that I might only have annual backup that I can restore. Freaked out right now.

Chris_QPW

@jr_ece others have been reporting such problems too, including for the R39.21 patch. I have also seen such complaints for older releases. I personally have not run into it thankfully, but since no one has ever found out exactly what is causing it, that is more luck than anything else.

The one thing I would certainly caution against is using Sync to Mobile/Web since it has been implicated in many such problems.

As for resolving this kind of problem, my go to, would be a backup. I certainly wouldn't be trying to fix them with any kind of edit or even Validate and Repair.

jr_ece

@Chris_QPW I was afraid of that response. As mentioned, I believe it has to be one of the recent updates running a conversion process or equivalent on paychecks. It has been years since I've tried to rollback. Will have to research to find the best path forward. Seems it would be uninstall, download latest full installer (shouldn't have R39.17 yet), and then recheck 3/9 backup prior to R39.17. If the backup already contains fouled paychecks to May 2006 then I can start trying to find a way backwards from there. Again, I don't think I have enough backups (limiting quicken to x backups due to size) so it might be a really old backup. In that case, I think it will take several days worth of work to reconcile an older backup with my latest quicken data file.

Chris_QPW

@jr_ece My assumption is in fact you don't need any other backup then the one before you updated to your current release.

Yes, the paycheck reminders are messed up back months, but that doesn't imply they were in fact messed up for all this time. Whatever caused the problem, can cause months or even year back of damage at that one point in time.

Chris_QPW

@jr_ece You probably need to revert your version of Quicken back to an older one before checking out if a backup has or doesn't have the problem.

I recommend that you reinstall Quicken from this link with your network connection disabled (don't start Quicken until after you patch it with the next step):
http://www.quicknperlwiz.com/install-for-quicken-2018---subscription.html

And then apply the version of your choice from here:
http://www.quicknperlwiz.com/quicken-subscription-patches.html

jr_ece

> @Chris_QPW said:
> @jr_ece My assumption is in fact you don't need any other backup then the one before you updated to your current release.
>
> Yes, the paycheck reminders are messed up back months, but that doesn't imply they were in fact messed up for all this time. Whatever caused the problem, can cause months or even year back of damage at that one point in time.

@Chris_QPW The assumption will depend on if a prior Quicken update fouled paychecks or if it was just R39.17. As for paychecks being fouled, I'm not talking about reminders. I'm talking about paycheck entries in my checking accounts (multiple accounts due to bank mergers beyond my control) going back to 5/12/2006. I've never seen this kind of Quicken data carnage ever. I have had corrupt files from (apparently) leaving Quicken running too long while stepping away, and I've had near term paycheck corruption as mentioned in another thread (usually 4-6 paychecks scattered over 3 or 4 months).

jr_ece

Just confirmed R39.17 was in fact the update that set all of my check entries to equal value back to 5/12/2006 (registry and reports showing I made the same amount from 5/2006 to present). I have R38.30 reinstalled and used a backup from late 3/8 since all I had done today was launch Quicken to see if there was a new update to fix the initial issue of this thread (unable to add tax field in paycheck). As previously mentioned, R39.17 did not fix this for me and caused bigger issues.

Chris_QPW

@jr_ece I'm glad that fixed it for you.

And yes, I mistakenly said reminders. I really meant the paycheck transactions in the register.

jr_ece

@Chris_QPW Ah, got you. Thanks for your help/support in working through the paycheck chaos. Sure hope this gets resolved quickly as I have paychecks stacking up for entry. Meanwhile, I'm researching other solutions...

jr_ece

Just occurred to me. Is there a better place or way to warn unsuspecting users that R39.17 could destroy existing paychecks back to 2006? I would like to help prevent others from losing hours chasing this one.

Chris_QPW

The main thread for that is this one:
https://community.quicken.com/discussion/7909601/r39-17-r39-21-paycheck-corruption-edited

And it definitely has a lot of warnings about it already.

Of course, the problem is will people see it or not. Forums like this really are very good for making everyone aware or such problems.

jr_ece

@Chris_QPW Thanks. Didn't see that one. Instead of relying on what I understand to really be a user driven support group it seems Quicken should have a way to alert users more directly. Maybe an email to the registered account??

Chris_QPW

jr_ece said:

@Chris_QPW Thanks. Didn't see that one. Instead of relying on what I understand to really be a user driven support group it seems Quicken should have a way to alert users more directly. Maybe an email to the registered account??

You might suggest that by going to the Home page and selecting New Post -> New Idea.

jr_ece

@Chris_QPW Good idea. Submitted.

https://community.quicken.com/discussion/7909912/issue-user-alert-for-quicken-updates-that-have-gone-awry/p1?new=1