https://www.quicken.com/support#contact-support
Please let me know
-Quicken Tyka
Quicken updated this morning, and I too am hit with all of these bogus overdue reminders.
Attached screen shot is from one checking account,
1. This is an online transfer of $125 from this checking account to a separate debit card at the same bank, originally posted and cleared 5/28/20, which now appears with a second entry still overdue.
2. This is a direct deposit paycheck entry into this checking account, originally received and posted 5/28/20, which now appears with a duplicate entry still overdue. The bottom line of this grid shows the next week’s posted check for $383.70, and newly appearing overdue entry for 279.68 (same amount as 5/29).
3. This is a credit card payment, originally posted 6/1/20. A second entry has now appeared, not “overdue” but rather “uncleared”.
4. This is a repeat of (1), the same transfer, with one entry that had cleared on 6/4, and a second entry now showing as overdue.
Based on insufficient information, my guess would be that my Chase download included data back to 5/28. Instead of matching downloaded records against previously download and cleared records, it treated them as new records, flagging some as if they had been entered by me and were waiting matching, and some as if they were overdue entries.
The Quicken file that I had the above problem with would have taken me hours and hours to clean up, with no assurance the problem wouldn’t recur on the next OSU. So I restored the file from auto-backup (3 days ago), and started experimenting.
Rather than a full OSU, I did a single update of a single checking account which has one recurring auto-transfer in. That account happens to be with a bank which has a single credit card also in Quicken, with two recurring charges and obviously recurring payments (and a recurring reminder to check for statements).
From the checking account I launched the update. It seemed to run normally. It pulled in yesterday’s transfer in (not yet matched since this is from a 3-day old backup), and there are no other bogus entries in this account. Accepted, reconciled, OK so far. Repeat the update. No changes, which is good.
Interestingly – OSU did not ask for my vault password.
Checked the credit card account. The register heading shows Last Download just now, express web connect. This account downloaded two new charges last night. Those new charges did NOT download just now. My future transactions all look normal.
Next test: Credit card which has a 0% balance transfer in it. There have been no charges in this account since the balance transfers. There have been six payments from the primary checking account, with future recurring payments (estimate: same as most recent payment) and a monthly reminder to check statements. Update that one account.
OSU now asks me for my vault password.
Following OSU, no changes.
Since it asked me for my password just now, and not earlier, I return to the first credit card with those two missing transaction, and update that account again. The two new transactions now downloaded, and nothing else happened. Looks good. Accepted the two transactions and reconciled. Good.
Next test: An online savings account that has one weekly transfer in. There had been one transfer in downloaded last night, and it downloaded correctly again during this test. Everything looks good.
Cross fingers and launch global OSU. Ran normally, and the accounts hit by the problem earlier this morning did NOT suffer a recurrence.
So it seems recovering to a backup file (which happened to predate the Quicken update), and running a new OSU on that, seems to avoid the issue.
I have two other Quicken files to process (I manage finances for three related families), and will update if I see anything significant while processing those.
