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

Account balance in report does not match register balance

BlackDuck2

Windows 11 R60.15, 27.1.60.15

Create report using Reports>Net Worth and Balances>Account Balances.

One checking account reconciled balance does not match the report balance shown. It's off by >+$80,000.

I don't know when this problem started as I haven't used this report in a while.

This checking account does include paychecks entered using paycheck wizard, and the account itself is over 10 years old. I can't find any paycheck discrepancies as decribed in the known paycheck issues problem.

I don't know how to find where the error first occurs.

Thanks for your help.

Find more posts tagged with

Reports

balances

Comments

Bob_L

Have you tried stepping back in time on the 2 reports for various dates to see if that shows where it occurs? Also I suggest you validate your file from the file menu in case there is corruption.

Edit: the two reports should pull the same data so it's not clear there will be a point in time where discrepancy shows up. Have you double checked the report settings?

BlackDuck2

Well, I started looking at old paychecks, all the way back to 2013, and found that all the detail in the paycheck splits associated with the paycheck wizard had been replaced by data from 2022. So that means years and years of paychecks that I will have to adjust to fix this problem, because in 2022 when I guess this Quicken paycheck corruption bug happened, I didn't know it happened, and I don't have backup from then.

Here are the links where I found the discusstion of paycheck problem:

https://community.quicken.com/discussion/7909601/r39-17-r39-21-paycheck-corruption-edited

https://community.quicken.com/discussion/7912649/paycheck-corruption-problem

Bob_L

Yeah, sorry I should have remembered that symptom. If I were you I would contact support to see if they can offer suggestions as to how to attack your situation, given the amount of data involved, and what other, if any, steps you should take.