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

Online recurring payments assigned to wrong account + other issues [Edited]

FlaSheridn

After the recent update to Windows Quicken R64.25/27.1.64.25, my online payments have multiple bugs. During the upgrade process, the was an error re-linking one of my Fidelity accounts, so I had to restore from a backup. Now all my online recurring payments are assigned to the wrong account, some old payments (perhaps with dates in the distant future) appear, and the payment amounts are wrong.

Find more posts tagged with

Windows

Online Bills

Comments

Quicken Kristina

Hello @FlaSheridn,

Thank you for letting us know you're seeing multiple issues with online payments. To clarify, did all of these issues start after you restored the backup, or were they present before restoring the backup also?

Since you mention these are recurring payments, are they linked to a reminder? Is the wrong information coming from the reminder series that they're linked to? Are the wrong payment amounts coming from old payments that are showing up again?

I look forward to your reply!

wildnut

Please see the following post. If you have a backup before the R64.25 release, what I did was uninstall Quicken and download it again making sure it doesn't do an update (turn off wifi on your computer upon starting the install).

Then, I restored from a known good backup. Just uninstalling and reinstalling Quicken didn't fix my problem as the update corrupted many of my Bill and Income Reminders.

I also don't have sync on (ie sync to the web/mobile) as in the past it caused multiple issues.

See this:

https://community.quicken.com/discussion/7965586/bills-income-reminders-issues-after-r64-23-update-past-due-duplicates-etc

[Edited - Enabled Link]

Quicken Kristina

Hello @wildnut,

Thank you for sharing the solution that worked for you! Hopefully this will help others encountering similar issues.

Thank you!