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

Thanks for escalating this, ​@ZackE_ . I do appreciate it. Alas, there are no “next steps toward getting [my] Bank Feeds stable and running again” until Intuit solves the problem. As you’ll see from my post below, there’s also no (official) WebConnect workaround, despite the agent’s promises to the contrary. I appreciate your proactiveness in escalating my issue, and request that you also escalate the critical inaccuracy in Intuit’s FIs-that-support-WebConnect document described below for correction, as this isn’t the first time I’ve received this misinformation from Intuit.

I was contacted today by Intuit. My email address was recorded and I am supposed to be notified directly when the problem is resolved, which the tech said should be within a week. Hope that’s correct. It’s been going on at least several weeks.

I want to pass along to lurkers and ESPECIALLY Intuit support that the “workaround” proposed is nonsense: To download WebConnect files from Bank of America.

Bank of America does not offer WebConnect files.

I’ve gotten the same advice multiple times for my (several) OLB problems. EVERY time, I follow up with BofA OLB support and get the same answer: BofA does NOT offer WebConnect files.

The agent didn’t believe me. They never do. They have an Intuit document that lists FI’s that support WebConnect, and BofA is on that list, even though it doesn’t belong there. 

But, hope springs eternal, so I called BofA OLB support (again) and got the same answer (again).

Here’s graphic proof. This is from the BofA web site, with the problem account open to the Statements tab, and this is what I see when I click on June 2026:

I can view a PDF. I can download a PDF. But I cannot download a WebConnect file.

Intuit: You MUST remove BofA from that list. OLB problems are frustrating enough without being told there’s a workaround that doesn’t exist.

And since there isn’t a workaround, Intuit needs to expedite this resolution.

Per the Intuit agent, Bank of America - New will continue working until this is resolved. So if you have any QB files you haven’t converted, as I do, you should still be able to download, despite the dire warnings we’ve all gotten that we have to switch by 7 Jul or we won’t be able to d/l anymore.

I replied to an email I had received from support shortly before this call providing this information about BofA & WebConnect. My case had already been closed, so it bounced!😡

Well, OK, there is a workaround. Not one Intuit would likely support, but IME it does work. YMMV. Make a QB backup first until you have confidence in it. I’ve gotten to where I trust it.

I have no connection to this product or the company that makes it, except as a happy customer. 

ProperConvert by ProperSoft - Extract and Import Transactions will convert a BofA statement PDF to a WebConnect *.QBO file. I’ve used it many times on a different QB file that has 1 BofA OLB-enabled account that doesn’t work with (BofA - New) Express WebConnect. It says it can OCR a scanned paper statement, which I’ve never tried. I always download the digital PDF from BofA because OCR isn’t 100% reliable.

Its retro Windows 98-esque UX will be comforting and familiar to QBDT users, and it involves a few more steps than Express WebConnect, but you won’t care about any of that once you have your .QBO file imported!

I just tried it with my BofA QBDT-borked company file and got everything from my June statement.

HTH.

​@JimFromAustin 

I appreciate your detailed information and can confirm there's currently an ongoing investigation about the Bank of American - QBDT connection issues.

I’ve added your account to our list of affected users for the investigation. This ensures you’ll receive email notifications about any updates relating to it while our Product Investigations team works toward a resolution.

Be sure to review our Receive important email messages from Intuit article to make sure you’re successfully receiving your update emails.

I think you forgot a “1”. 

Speculation here, because my data set is small. But my personal BofA checking/savings accounts don’t offer WebConnect files. Only my business checking/savings accounts. If you use a personal account for your business, that may be why you’re not seeing it.

I don’t have a BofA personal credit card anymore so I don’t know about those. For business credit card accounts, you have to select a specific CC account (corp account or employee card accounts) to get a WebConnect file.

Assuming you have personal accounts, ProperConvert (see my post above) says it can convert XL files to QBO. I’ve never tried it, but if it can extract data from bank statement PDFs and turn it into QBO files accurately, XL conversions would be a MUCH easier problem to solve programmatically, so I’d think it would work well.

Or you could use it to convert your bank statements...although BofA personal accounts combine checking and savings statements on one form. ProperConvert won’t separate them, so you’d need to select specific transactions for each account to export during the conversion. Probably not too difficult because they’re presented sequentially as they appear in the statement.

Yep, it will take hours to sort out the duplicate transactions going back who knows how far.  

I honestly don’t think this is all on QB.  It’s the change from Bank of America-New to Band of America-QBDT that seems to be the issue.  After three hours on the phone with BOA and Intuit support techs, 1 hour at the same time, BOA seemed far more knowledgable of the problem and mentioned that their techs were working on getting it fixed.  Not that I’m any kind of fan of QB but I don’t think this is totally on them from what I could glean over three hours.