I upgraded to QBDT pro 2024 and my bank feeds stopped working. I get OL-232 error.

Install the trial version of QB Desktop 2024 Enterprise to compare. Did you encounter the same problem?

I am working with a QuickBooks help desk person for past 3 days. She said not to upgrade to the trial enterprise version and the problem is with the bank, not QB.

Called the bank multiple times (via phone, supervisor escalations, emails) they say if my login is working from a browser then there should be no issue. There is no special approval, no extra service to be added. If it was working with QBDT2022 and stopped working when I upgraded to QBDT2024 then it is QB problem.

After disconnecting the bank feeds from my bank account I now get error OLSU1013. QB says that is bank's issue. They are not validating sign on. 

One key item - after trying multiple times via QB login,  the bank uid login gets revoked/disabled so apparently QB and bank are talking so no firewall issues. I wonder if there is some MFA happening and QB has not taken into account all possible responses a bank can give. Or Bank does not 'trust'  login request via QBDT2024 as it did QBDT2022.

Back and forth like a football between the two helps desks.  I am paying > $1000 for QBDT subscription annually for what? The bank connections that do not work?  And for a supported QBDT version that does me no good because they apparently have not even tested QBDT2024 with fifth third bank acct logins. QB used to be way better 2012-2019, it is now charging arm and leg and working worse. There are so many versions of QB, no wonder the support staff cant really help.

I see many problems reported similarly over past couple of  years and QB said developers were on it. Does anyone have a case where these get resolved? Or do people just give up , change banks or accounting software? 

You should consider our suggestion to use the trial version to be sure.

Last resort, use qfx2qbo converter tool. It's a $60 one time license. Then you may consider switching to an old QB Desktop with a non subscription license before the renewal date of your current license.

https://www.moneythumb.com/?ref=110

QB launched an update that ended up mixing some fields up in their database and caused your customer ID for your bank feed login to be changed by a regex that formatted your bank login ID as if it was  SS# or EIN and also changed EIN to be a 4-digit chart of accounts reference number or something similar. In essence, you will need to contact quickbooks support, explain the issue, and submit your company file for data repair services as QB desktop will not allow you to change your customer ID due to the EIN and Customer ID being the wrong format, giving an error when trying to save, and not allowing you to actually save any changes.

There's a support guide that explains that you can change or deactivate your bank feeds by exporting your chart of accounts as an IIF file, modifying the relevant lines, and importing the updated IIF file but this still errors due to the above reasons. Basically, someone at Intuit made a mistake, pushed an update that caused this issue, and either hasn't realized the issue yet, or the issue can't be fixed by pushing a new update due to the fact that it changed your existing ID and EIN / SS# for those fields and they can't simply reverse it with an update. 

I've not tried this but it's possible you could revert to a back up prior to when you started to experience this issue and that might fix the problem but you'll have to re-enter all the data since that time such as bills, invoices, etc. I've contacted support about this and am waiting for a response from the data recovery team to help fix the file for me.