Error: ACCOUNT_NOT_FOUND (324) and Transactions show "Check" for All Payees [Edited]

Rob Kurth

Quicken Classic for MAC started failing account update last week. Each time I try I receive this error "A name or number for your Vermont Federal Credit Union account may have changed. Let’s fix the issue by reconnecting your account. (324)". I can reconnect the account, but when transactions download the Payee field for all transactions is "Check". This combination of problems makes Quicken unusable.

eastmanm2172

I am having this same issue but with my main banking account at Yolo Federal Credit Union

eastmanm2172

Since about 11/17/24 my main checking account at Yolo Federal Credit Union will not connect and says that the connection needs to be fixed….ACCOUNT_NOT_FOUND (324). I disconnected and then reconnected the account and can get a single download; however, the payee only shows date, "Check" as payee, and value. I thought this was an issue with the bank, but see that at least one other person is reporting a similar issue.

This has been going on a few days. When I try to update the account, this error and process starts all over again….

Quicken Anja

Hello @Rob Kurth and @eastmanm2172,

We will be forwarding this issue to the proper channels to have this further investigated. However, we request that you please navigate to Help > Report a problem within your Quicken program and submit a problem report with log files and screenshots attached in order to contribute to the investigation. It would also aid the investigation to include a sanitized file when submitting the problem report. A sanitized file is a data file that removes personally identifiable information so you can comfortably share this file with the Quicken team.

While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.

We apologize for any inconvenience in the meantime! Thank you.

Quicken Anja

Hello again,

This issue has been reported to our Development and Product teams for further investigation and resolution. Though we do not currently have an ETA, once a solution is created it will be made available as part of a future release.

Thank you!
(CBT-448)