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

Copy/Paste Paycheck for Bonus Messes Up All Past Paychecks

BryanK

Using R39.23

Hi I know this issue has been documented. To record a bonus received on Feb.28 I copied/pasted a past paycheck on Feb.11 in the register, opened it and entered my bonus amounts and saved. Unknown to me until just recently, doing that messed up all my past paycheck data! Now in the Tax Summary all my past paycheck show the same amounts from as the paycheck that was copied (before modifying for bonus) as if my copied paycheck overwrote all past data.

In the register itself the past paychecks show the correct amount in the register display, but when I select the transaction line and click the "split" button the transaction that comes up for editing has the same values as the original copied paycheck (before modifying for bonus).

Serious bug here. I manually fixed all my paychecks year-to-date, but prior year paychecks have all been overwritten apparently with the data from the copied/pasted paycheck.

Are the developers aware of this issue and will "Super Validation" fix it? Are there any one-off utilities to fix it without having to manually fix?

So this doesn't happen again, I followed the advice from a similar thread to enter the bonus as a separate annually scheduled paycheck.

Find more posts tagged with

Add/Edit Transactions

Known Issues

Comments

Chris_QPW

What you are seeing might not be directly related to you copying a paycheck. The corruption might have already been in your data file if at any time used R39.17 or R39.21.

See if this thread is rings a bell:
https://community.quicken.com/discussion/comment/20254313/#Comment_20254313

Note before posting this I did try copying a paycheck in my register and had no problem.

BryanK

Thanks, that seems to describe what I was seeing. Looks like only 2022 year-to-date and 2021 paychecks were affected for me. I was able to manually fix and will be taking on a way more aggressive backup strategy

Chris_QPW

BryanK said:

Thanks, that seems to describe what I was seeing. Looks like only 2022 year-to-date and 2021 paychecks were affected for me. I was able to manually fix and will be taking on a way more aggressive backup strategy

At a minimum I would run Validate and Repair to see if the problem gets worse, as it did for me.
Personally, wouldn't trust just manually fixing the paychecks. No telling what other problems are in there.
Instead, I restored from a backup before I used R39.17, on 3/4/2022, and then redid what I had done from that point on.

BryanK

OK I found a backup from 2/25 and will bring it up to date thanks

BryanK

OK Chris it was painful to bring a month-old file current, but now I have a good file that pre-dates the corruption. This little incident has definitely ramped up my paranoia as far as a backup strategy ....

Chris_QPW

BryanK said:

OK Chris it was painful to bring a month-old file current, but now I have a good file that pre-dates the corruption. This little incident has definitely ramped up my paranoia as far as a backup strategy ....

Yeah, that is never fun, but better safe than sorry. I'm glad you have it fixed.