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

Quicken suddenly started downloading pending (not posted) transactions

swqca

Hi, a couple of days ago, Quicken suddenly started downloading "pending" (ie., "authorized" but not "posted") transactions. I have never used or enabled Pending transaction in the app, and have confirmed that Pending Transactions are turned off globally in settings.

This is extremely annoying because now the Online Balance never matches the Ending Balance for my credit cards. My bank accounts have also started downloading transactions as soon as they occur, but this is less of an issue for the bank accounts because the Online Balance is also updated to reflect them.

Both my credit cards are from the same bank (RBC - Royal Bank of Canada). I don't have credit cards (or bank accounts) with any other bank to check if this issue is bank-specific.

When this problem started happening I was on Quicken v54 (and had been using it for several weeks or months). I've now updated to v57.16 (build 27.1.57.16) and the issue persists.

Some troubleshooting steps I've tried:

downloading credit card transactions in CSV and also QFX format from the RBC banking website. Pending transactions do NOT appear in the downloaded files.
restoring from a backup from a few weeks ago. But the next time I download transactions it still pulls in pending transactions.
enabled and then disabled Pending transactions in Quicken settings. Did not make a difference.

Has anyone experienced this? I don't know if it's a problem with Quicken or with the bank's online services.

Thanks,

Simon.

Find more posts tagged with

Comments

swqca

Update: The issue is also happening for my bank accounts, not just my credit cards.

UKR

If you haven't done so already, please do the following actions:

Even if you are on the latest software level already, download and install the latest Manual Patch file from https://www.quicken.com/support/update-and-patch-20182019-release-quicken-windows-subscription-product to ensure your Quicken software is up to date and correctly installed.
Reboot Windows.
Start Quicken. Do not run One Step Update.
Run BOTH Validate and Supervalidate to attempt to repair your Quicken data file.
If nothing helps, try to restore your Quicken data file from an Automatic or Manual backup taken just prior to the problems first occurring. https://www.quicken.com/support/how-backup-or-restore-your-quicken-data

Validate and Supervalidate instructions
First save a backup file prior to performing these steps
Validate:
• Click File
• Select Validate and Repair File...
• Select Validate File
• If the data file contains investment accounts also select "Rebuild investing lots".
• If you suspect that a damaged Quotes Price History causes your problems, also select "Correct investing price history" functions "Delete" or "Repair and Rebuild".
• Click OK
• Review the Data Log. Anything interesting in there, worthwhile posting here?
• Close Quicken, leave it closed for about 30 secs
• Reopen Quicken and see if the issue persists.

Super Validate:
• Click File
• Press and hold both CTRL and Shift keys while you click Validate and Repair File...
• Select Supervalidate File
• Click OK
• Review the Data Log. Anything interesting in there, worthwhile posting here?
• Close Quicken, leave it closed for about 30 secs
• Reopen Quicken and see if the issue persists.

swqca

I looked into applying the manual patch, but it is a version behind what I already have installed. My currently installed version is 57.16, but the patch is Release R56.9 (Canada Versions, May 2024). Additionally, if I launch the patch installer it says, "The version of Quicken installed on this computer is 2018 R1." That does not seem right - I have cancelled the patch installation.

Please advise.

swqca

I ran validate and super validate as per above steps. Nothing interesting in the log output to report. The issue still persists.