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

Merrill Lynch FDP-105 Error

MightyIrish

Merrill Lynch Benefits Online has been returning the following error for 4 days now:

Account needs attention

(Care code: FDP-105)

We are unable to connect to Merrill Lynch Benefits OnLine at this time. Please try again later.

Find more posts tagged with

Online Banking

Comments

Coach Natalie

@MightyIrish, thanks for reaching out to the community with this issue! We're happy to look into this with you and troubleshoot.

I confirmed the FDP-105 error with Merrill Lynch Benefits OnLine while reviewing your connection attempts on our end. It looks like the error first began on 9/19/26. This error occurs when our connection to your bank is throttled, limiting successful connection attempts, or when a server outage occurs. More details can be found here: https://support.simplifi.quicken.com/en/articles/13795819-errors-fdp-102-fdp-105-when-using-online-services-in-quicken-simplifi

To start, I recommend establishing a completely fresh connection with the bank and getting a new access token to see whether that clears things up. This will also allow us to confirm the error. Here are the steps to follow:

Navigate to the bank's website, sign in, and remove Quicken's access from the bank's third-party linked apps.
Navigate back to Quicken Simplifi and make all of the accounts with this bank manual by following the steps here.
Once you see the account(s) listed in the Manual Accounts section under Settings > Accounts, go back through the Add Account flow to reconnect to the bank.
Carefully link the account(s) found to your existing Quicken Simplifi account(s) by following the steps here.

Let us know how things go!

MightyIrish

Same error after following these steps

Coach Natalie

@MightyIrish, thank you for giving those steps a try and posting back!

The next step is to allow 48 hours to see whether the error resolves on its own. Since it's already been more than 48 hours, I recommend contacting our Support team directly for more advanced help, as they have the tools to gather any needed data and determine the best path forward.

Let us know how things go with Support in case it's helpful for other users!