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

Bank of America is transitioning accounts to a new connection method.

Frank DeMello

When I tried to update to the new connection method today, I received the error below:

I have spent a few hours on the phone with Bank Of America technical support and they indicate they see nothing that could cause this and it is on Quicken't end

Please advise & thank you

Find more posts tagged with

Known Issues

Quicken Mac

Linking

download transactions

Comments

Quicken Kristina

Hello @Frank DeMello,

Thank you for taking the time to report this issue to the Community, although we apologize for any frustration or inconvenience experienced.

This issue has been reported to our Development and Product teams for further investigation and resolution. Though we do not currently have an ETA, you can bookmark the Community Alert linked below to get updates when available and to know when the issue is resolved. If you do not see the bookmark icon at the upper right, please make sure you are logged into the Community.

https://community.quicken.com/discussion/7971544/new-2-26-26-user-not-eligible-bank-of-america

Per the alert, this issue typically happens when the account is a shared account (primary account holder and one or more authorized users). Please make sure you are connecting the account using the primary account holders credentials. If the issue persists, please contact Quicken Support directly for assistance, as they have tools we can't access on the Community and they're able to escalate the issue as needed. The Quicken Support phone number can be found through this link here. Phone support is available from 5:00 am PT to 5:00 pm PT, Monday through Friday.

I hope this helps!

Frank DeMello

Thank you. Will contact support.

Just an aside on this error: this same exact error due to primary/secondary account holders is happening on another platform (EMoney). And I am not the secondary account holder.

I have called BA tech support 3 times and they have no clue about what is happening

kuliano

I've been getting the same error since the BOA connection method update. I have a ticket open with Quicken and was told by the last rep I called on 3/2 that this was (presumably) tied to an overarching ticket and escalated since many users are reporting this issue. I was also told this will likely be a back end resolution vs a client side push. Does anyone has any additional information and/or update? This is so frustrating!

DPTrainor

There is much false information going around about this Bank of America situation. There is no clear diagnosis of the root cause known and no remedies to-date. But, I hope they come up with a solution quickly.

DonnyD

I am experiencing the same issue and have contacted support at both Bank of America and Quicken. Unfortunately, neither side seems to have a clear resolution. Each points to the other as the source of the problem, which leaves users stuck in the middle.

What is especially frustrating is that Quicken is now a subscription service. With that model, I would expect issues like this to receive prompt attention and resolution. Reliable connectivity to financial institutions is a core function of the software.

I have used Quicken for many years and have always appreciated it, but situations like this make me question what alternatives might be available if this problem continues unresolved.

Mike Schuster

It is still not resolved! I am still experiencing this issue which really impacts the usefulness of the program. It is going on a week and it is unnacceptable that this is not resolved. I have used Quicken for over 20 years and am now actively looking for an alternative. I would expect some sort of credit to our 'subscription fee' for something this significant and that has been allowed to persist this long.

Quicken Kristina

Thank you for the follow-up,

I can see that all of you have already contacted Support about this issue. If you haven't done so already, please bookmark the Community Alert to be notified of updates, once available, and to know when the issue is resolved.

Thank you for your patience as we work to resolve this issue!