Schwab - Re-authorizing account access results in duplicate transactions

Thomas Hyzy

Performing this morning's (5/7/25) One Step Update resulted in Quicken requiring me to re-authorize all of my Schwab accounts. That process went smoothly. However, when the update ran afterward, suddenly one Quicken account balance was off by over $2k from the "true" Schwab balance. This account reconciled to the penny yesterday. By some rather arduous comparison of the transactions posted in both places, I was able to identify 2 cash transactions that had been duplicated. These transactions were from February 2025, which is truly puzzling - why these 2 payments (one a utility EFT, the other a credit card payment, 2 different payees), and why from February? I have no answers to these questions, my point in posting this is to warn other users of this potential issue.

Quicken Jasmine

Hello @Thomas Hyzy,

Thanks for sharing!

What you described—duplicate cash transactions appearing after reauthorization—is something that can occasionally happen due to how the financial institution sends historical transaction data back to Quicken. Even though the reauthorization process completes successfully, Quicken may receive older transactions again if the financial institution’s system flags them as “new,” especially if internal IDs or metadata have changed.

Unfortunately, there’s no clear reason why only those two February transactions were affected.

To resolve this:

1. Delete the duplicates manually if you're confident you've identified them correctly.
2. Use the Downloaded ID column (enable it via the gear icon > Register Columns…) to help compare and detect duplicate transactions in the future.

If you're willing, please submit a problem report so I can review your log files:

1. Go to Help > Report a Problem.
2. In the description, reference this duplicate transaction issue following Schwab reauthorization.
3. Check the boxes to include:
   • OFX Log
   • ConnLog.txt
   • Sync Log
4. If possible, attach screenshots of the duplicate transactions for context.
5. Click Send to Quicken.

While we can’t guarantee the logs will pinpoint the exact cause, they may provide valuable clues.

Let me know!