Seven accounts not reconciling after correcting CC-800 error [Edited]

MichiganChuck

I am using Quicken Classic Deluxe on Windows 11, Version R65.29, Build 27.1.65.29

I have been using Quicken since 2005. I download and reconcile almost daily.

Today after downloading to update the accounts using Express Web Connect, seven of the credit card accounts returned a CC 800 error, indicating what I interpreted to be an account deleted or installation of a backup file, neither of which I did. Only seven credit cards are set up to automatically update. The three banks with checking accounts performed normally.

As recommended for a CC 800 error, I deactivated and reactivated the accounts, then updated the accounts. The problem is after that update the credit card balances no longer reconcile. For example, before today's update, the balance on Quicken for one of the credit cards for 1/17/26 was -5868.74 and the account successfully reconciled on 1/21/26. After today's update the balance for 1/17/26 was -5615.27 with no new transactions prior to 1/17/26. Somehow the account was reduced by 253.47 and would no longer reconcile. (The reconcile showed a difference of 278.47 but I haven't figured out that $15 difference.)

The update of accounts the prior day acted strange, taking over twice as long as usual and had no new transactions. The incorrect balance after updating accounts also happened a couple years ago, but I just made balancing transactions and ignored the issue.

Is this just a quirk I should ignore? Or is my database corrupted and some other action is necessary?

NotACPA

There's a long standing bug in Q, for which the precise cause hasn't yet been ID'd, that when your change the download into an account (incl de/re-activating) the Opening Balance sometimes get changed.

What you'll probably need to do is to restore a backup (to a different name so as to not overwrite your current file) and determine what that OB should be … and then correct the OB in the current production file.

It's also suggested that you record the correct OB for each downloaded account in the Memo field of the transaction … so that if this happens again you can quickly ID the correct amount without having to use a backup.

Also, look for duplicated transactions in the account. Some FI's (who are responsible for creating the FITID of a transaction) don't maintain the same FITID on a subsequent download. It's via the FITID (Financial Inst Txn ID) that Q is able to spot dupes. And if that FITID differs, Q can't match the 2nd download of a txn to the 1st and know that it's a dupe.