Issue With Reconciling Paycheck Transactions

System

This discussion was created from comments split from: Paycheck Transactions changed.

wi_muggs

I have the same issue. Could not figure out why my reconciliation of my checking account was messed up. Found Paycheck transactions where moved to different dates and the amounts were changed. I corrected some, but still have others that show all zeros in the breakdown when I try to edit them.

Unfortunately my backup was from awhile ago and it will be a lot of work to reconcile the accounts again.

Tried running validation and it did not fix the issue. Found a lot of other corrupted data.

wi_muggs

Quicken Support was useless on this issue. All they can tell me is to restore from a backup.

Quicken Jared

Hello @wi_muggs ,

We are sorry about this problem with reconciling transactions. Thank you for alerting us to this problem here on the Quicken Community.

I see that you have mentioned attempting to validate the data file, but has a Super Validation also been attempted? First, save a backup by navigating to File > Copy or Backup File… in the upper menu at the top of the screen, then try proceeding through the instructions listed below, if you haven't already:

1. Navigate to File
2. Hold CTRL + Shift and click Validate and Repair File…
3. Select Super Validate File 
4. Click OK
5. Close the Data Log
6. Close Quicken (leave it closed for at least 5 secs)
7. Reopen Quicken and see if the issue persists.

Let us know how this works!
Thank you,

Quicken Jared

wi_muggs

I was able to restore a file from 2/4. In the backup the paycheck transactions are on the correct days and amounts, but the details/breakdowns show all zeros when I try to edit them. But when I hover the mouse pointer over the transaction it shows that correct amounts.

If anyone from Quicken would like to research this issue please let me know.

System

This discussion was created from comments split from: Paycheck Transactions changed.

NotACPA

What BUILD of Q are you running? Do HELP, About Quicken for this info.

This sounds like a bug that was corrected a while back.