Bank of America reporting fdp-390

Jrunner01

I opened simplifi today and noticed my BOA credit account had a error. So I followed the message to re-authenticate it with it said was a new method. After going through the steps it now says fdp-390. I tried 3 times same outcome.

I assume this had something to do with the may 6th issues but I don't think I ever saw that as I haven't logged in till after that issue.

Also says now care:.api.database.accountkey.notfound.

SRC54

Try making the BOA account manual, and re-adding it using the + Accounts. If that doesn't work, try to establish a new connection through the Phone App instead of the web app.

You may find reading this conversation useful.

https://community.simplifimoney.com/discussion/12362/vanguard-fdp-390-error-still-occurring

Jrunner01

Thanks src-54 for the tips. I was able to fix it. Part of what I think I was doing wrong initially was when I was using the phone app to fix this I was accidentally authenticating to my bank with a login account that doesn't have access to the credit card. I have a second login account to the bank that does have access to the credit card and I wasn't using that one to reauthenticate during that first initial process to fix the account connection message when first logging in to QS today.

I caught myself remembering the different bank account logins, with which types of BOA accounts are available to that login, when I went to make it manual and add it back as you suggested. I think a combination of using the right login account for the bank and the fact that I was going through the manual and re add process is what finally fixed it.

SRC54

These broken bank connections can be vexing. Glad you were able to fix it!

Jrunner01

https://community.simplifimoney.com/discussion/comment/69661#Comment_69661

Yeah definitely, with a number of times I've had issues with accounts not connecting properly in the last six to eight months that I've used this service I immediately thought well here we go again. Well I'm kind of Justified in saying that because like I said I logged in today and there wasn't initial connection issue that didn't resolve itself from whatever maybe happened on May 6th. But then I went and messed it up using the wrong account login. So yes this one was on me but the initial one is still on the service with its usual problems of accounts not connecting or connecting incorrectly and downloading the wrong amount of transactions and duplicates in yada yada yada. I guess I'm just tired of this service with all the issues I've seen over the time I've had it which is just under a year.