Bank of America – QBDT connection crashes after OAuth; error 88888 in affected company file

Please add me too. I am experiencing the same problem with my expensive subscription for QB Enterprise Desktop Version. I also have a case #15162969687 with Bank of America. This issue is more than a month!

I tried yesterday to reset my QB ID and reconnect accounts with BofA. I got the same problem with crashing my QB and when I restart and tried again. I got 88888 error message.

I have 4 companies files with over 18 BofA accounts. All of them are not working now. It is a total disaster.  Please let me know if someone was successful with any resolution to this problem.

Please add me to the unhappy frustrated QB-BofA customers. I was with QB over 22 years and never had so bad and long issue not being resolve.

Just received an Update which they have said they identified the root cause with BOA and Syncing - 

I’m having the same issue, Quick Books desktop 2024. I get as far as connection between Bank of America accounts to the accounts in my file. But the status says “not added OLSU1034” .  Web connect files work but I have to log into the bank every time.  Nothing is automatic like its supposed to be.

We are all in the same boat regarding the Bank Feeds to Bank of America, specifically why the “Bank of America - New” portal was disabled when Intuit knew that the “Bank of America - QBDT” did not function.

  It is frustrating to hear the repeated suggestion of a “work-around” (while BOA and Intuit get their act together) of downloading a WebConnect file from BOA.  BOA offers no WebConnect download format for “personal” accounts, only “business” accounts.  “Personal” accounts include trust accounts which is a big part of our operation.

But, after writing to the President’s office at Intuit, I received this reply which seems to be the most cogent communication posted on this thread:

“I appreciate the response with further info! I do apologize that there isn't the option for Web Connect in this case, that is something Bank of America would need to implement in accordance to our OFX Connectivity Group (which is to say, BoA would need to follow the escalation path via https://ofx-partner.intuit.com/), though I can't say I'm certain as to why they would only have it as an option for business accounts.

For clarification, the transition from "Bank of America - New" to "Bank of America QBDT" is the result of Bank of America upgrading it's data-sharing infrastructure while deprecating its legacy DDA API. We are transitioning in accordance with the new security and stability measures. Suffice it to say, we are working with Bank of America to get it resolved. Though the transition itself has been problematic, this issue hasn't flown under the radar and it has high priority with the Product Development team. As of right now, they have identified the root of the issue and are acting accordingly, so hopefully it won't take too long now to get a fix rolled out.”

One of the LARGEST banks in the USA and one of the largest accounting software companies, not playing nice… NOT surprised!

How is QBO connecting to BofA?…  Because if this is an effort, again, by Intuit to force us to make a choice to move to QBO, … well they have another thing coming!  I’ll move all my clients to another software company well before I move to the piece of junk QBO!

This is a complete joke Intuit, this should not take this long to fix, and it shouldn’t have happened in the first place!  You should have never gone live with the change, not knowing what it would do!  What happened to your internal BETA testing? wow!

I have a LARGE client right now, lots of transactions, and this was the fastest way to close out their month and now we are stalled and then proceed to do an archaic way of doing it.  GEE thanks for wasting our time Intuit.

A month since my OP, 2 or 3 months since I first tried to migrate to Bank of America QBDT, and who knows how many angry “me too” posts on this thread, I received an email today from Intuit saying the problem is fixed with the current update. Better late than never.

Opened QB and clicked Help->Update Quickbooks Desktop. No new updates had been downloaded. Clicked Update Now and a large Critical Fix update downloaded. Closed & reopened QB to install it. Then backed up a company file, removed its OLB connections set up by manual WebConnect imports. 

Then took a deep breath and set up OLB on my BofA accounts.

And I’m pleased to report it worked!

Lots of duplicates to delete from my manual WebConnect file imports, and 3 more company files to go after this one. But once that’s sorted out, life in QB can go back to what passes for normal.

I just received this from Intuit » We’re reaching out to you about a recent issue you reported: QuickBooks Desktop crashes or throws an 88888 error when attempting to connect to Bank of America QBDT. Good news! We reviewed your case, and we're happy to say this issue was resolved with our latest release of QuickBooks Desktop.

To make sure you have the most up-to-date information, please update your QuickBooks Desktop to the latest release.

ITS FIXED with Bank of America, was able to reconnect all the accounts. It downloaded about 2 months of transactions so you just have to clean them up, if you have them in your books already, just select INGNORE, if you have many like we did and they are all in your books, you can select them like a batch and select IGNORE…..FINALLY FIXED

ITS FIXED. Was able to reconnect. Of course a bunch of old transactions got downloaded that needed to be deleted. What a pain in the butt!

Still not fixed for me even after updating QB.  And now to try again I have to ignore 200+ banking transactions.  NOT happy and zero follow up by QuickBooks.