Hi @knapiks,

I understand how the Save option would help provide a more customer-friendly interface. However, this option is currently unavailable. Rest assured, your encounter will be shared with our Developers. 

I suggest sending a product request via this link: feedback.intuit.com

On this site, you'll also see updated ideas added to QuickBooks.

Please know that you're always welcome to swing by anytime if you still have questions or concerns with bank transactions. Take care and have a lovely day ahead.

 So how do I save them manually?  It just goes directly to Qb's - or doesn't.  I didn't see this in the link you sent.

So how do I save the file?  I didn't see that in the link you sent.

Thanks for coming back, @knapiks. Please ensure your QuickBooks is updated to its latest release to ensure you have the latest features and fixes. 

Then, open a sample file to check if you have the Save option. If it's there, that means you'll need to troubleshoot this unusual behavior by running the Verify Rebuild tool. 

Here's how: 

Run the Rebuild Utility

1. From the QuickBooks Utilities menu, choose Rebuild Data.
2. Click OK if you receive a prompt to back up your company file.
3. Select OK when you get the message Rebuild has completed and proceed with the next step.

Run the Verify Utility

1. Go to the File menu, select Utilities, then choose Verify Data.
2. Select OK when you see the message QuickBooks detected no problem with your data. You may continue using your company file.
3. If Verify finds an issue with your data, you will be prompted to Rebuild Now or View Errors. Select Rebuild Now.

If the issue persists, I'd suggest contacting our Customer Care team to help check your account and help you fix it. 

Keep in touch if you have additional concerns. It's always my pleasure to assist you.

I am a BBT (now Truist) client and have never had any issues importing the monthly .qbo file from the bank download.  That is until yesterday when everything changed.  Yesterday, all my troubles seemed so far away, now it looks as if they're hear to stay!  OK, so after 2 hours of texting with Intuit on Sunday and getting nowhere, Nowhere Man, please listen, I was able to speak with a live agent yesterday (Monday April 4, 2022).  We tried everything under the sun.  He had me editing fidir files - never heard of a fidir file before, but they do exist deep in the Intuit folder.  Still nothing.  Finally I called Truist and was able to have a 3-way [not that kind of 3-way - you have a dirty mind] a 3-way conversation with Intuit and Truist.  FINALLY I had the answer.  

Error OL-222 is NOT a Intuit issue, it is a known issue with Truist.  It all makes sense because I imported my February file last month with a problem.  But since then, Truist developed a glitch in generating the .qbo download file and they are aware of it and working hard to fix it.

The Workaround:  Luckily there is a way to bypass the error until they fix the issue.  It costs $14.95, and considering all the hours I spent chatting and on the phone with Intuit, it's a no-brainer.  I signed up for the direct bank feed from Truist to my quickbooks file and was able to import the entire month seamlessly.  

So, there you have it.  You cannot download the .qbo file but you can have the file beamed in to your computer for $14.95/month.  That will work until the OL-222 is fixed.

I appreciate you for sharing your experience and workaround in handling the error, @ROCHA corporation.

The information you've shared can help a lot of users who are experiencing the same issue.

In case you need assistance with your bank transactions or with QuickBooks, you can always add them in this thread. I'll be more than happy to help you. Take care and have a great day ahead!

Thanks for the post, been having the same issue for months...

Hey there, @justinj753.

I'm glad to hear your issue has been resolved. 

If you have other concern you can also to get in touch with our support team, you can refer to the steps outlined in this article: Contact QuickBooks Desktop support. Ensure to check their support hours to know their availability.

The Community always has your back and I am here to help you anytime. Have a good one.

Just came off of about my 5th hour with Truist support.  There is no general knowledge within their system about this type of problem.  However, they were happy to lead us through the deactivate/reactivate a bank account with their $14.95 per month option to allow us to use the qbo. download process that's not supposed to require a fee.

My synicism tells me that Truist will be very DISINCLINED to "work furiously" to solve the .qbo option because they cam scam enough of us into the monthly fee scheme that we shouldn't need.  Our request to talk to a supervisor/manager resulted in a transfer to a phone that was unanswered and had a full voicemail.

BTW, I examined ALL recent posts to twiggle the .qbo files that do not relate to the files that I'm looking at.  I examined our file from the prior month (successful import) with the current month (unsuccessful import with the dreaded OL-222 error).  There was no significant change from one file to the other in regards to paired tags and any "long names and extraneous characters".  I did excise the "erroneous" characters to receive the same error.

The account by account effect that many have been experiencing is more likely that Truist is incrementally converting individual account blocks into their "new and improved" system.

This is all laid to the alter of Truist and their ham-handed transition.  It will be painful but we'll probably be finding another bank.

Hi Guys, Heads up...

Now when we try to download our Checking transactions,  we get an error code OL-222 in Quickbooks. we upgraded to version 2022.

I was able to fix it using NotePad on Windows 11

This error code refers to Characters unrecognizable from QB in the Name field on the .QBO file from Bank system, like such:

<NAME>ETIQUETTE PROSCAN</NAME>

in order to get the file read into QB, i had to manually remove all the following characters in the "NAME" fields :  * . , : / And double space "  "

for example, if it looks like this, it will generate the error:

<NAME>ETIQUETTE: PROSCAN</NAME>

Or double space:

<NAME>ETIQUETTE   PROSCAN</NAME>

(Ridiculous!) 

The errors all were generated from the "Name" field, i did not touch anything else.

But of course out of 150 ish transaction, QB won't tell you which one is messing things up, so it took me 2 hours to figure it out and clean them.

Other research show that this error can also be generated by incompatible banking QBO file (probably hard to keep with all the updates on both sides) Pushing on my Bank to fix this ASAP haha

Hope that helps,

I am experiencing the same problem with TCF bank. I had edited the company file and I don't see any invalid characters. I am only using this method because the bank import stopped working about a month ago. I'm wondering if something changed when they merged with the new bank. If anyone knows the answer, I would appreciate hearing back.

Hi there, @DaveThomas2.

Aside from the invalid characters of your QuickBooks Web Connect (.qbo) file, you'll want to shorten the fields and texts. Then, add or edit missing markup. All tags in the file should have the following:

Keep in mind that if the Payee name field is longer than 32 characters, the rest of the info appears in the Memo field.
 

For additional advanced troubleshooting, check out this article: Fix Web Connect import errors.

Additionally, make sure your QuickBooks Desktop is up-to-date to have the latest features and fixes. 

Keep me posted on how these steps work out. I want to make sure you can continue working with your bank feeds. Have a nice day!

Thank You!!

I went in with a text editor and removed all the following characters in the "NAME" fields :  * . , : / And double space

And it worked!!!

None of this works for me, but import of a .qbo used to work PERFECTLY last year. I tried editing out any invalid char's as u suggested (e.g. &amp) but could find none in the .qbo file. I read all the other links for this issue and none of them makes any difference. I have a YEAR's worth of txn's to post and am in UTTER SHOCK that this method no longer works. Please advise ASAP.

So to solve this issue I have to share my financial info with some 3rd party??? Seems pathetic to me

You don't have to share your financial information, FAinc.

The bank error OL-222 may occur if there are any invalid characters or possible double spacing in your .QBO bank file. 

To fix it, you can open the file using a Notepad or any text editor available. Then, you can look for * . , : / And double space. This process may take some time since it depends on the size of your bank file.

Alternatively, you can use a 3rd party application to bring your transactions in QuickBooks. This method doesn't require you to provide any bank details. You can utilize this link to find a third party importer tools to import your bank transaction: QuickBooks Apps.

If the issue still persists, I recommend contacting our QuickBooks Desktop Support. They can do a screen sharing to guide you importing your bank transaction and submit a ticket for further investigation.

Here's how:

1. Open QuickBooks.
2. Go to Help, then select QuickBooks Desktop Help/Contact Us.
3. Click Contact Us.
4. Give a brief description of your issue, then select Continue.
5. Sign in to your Intuit account and select Continue and then Continue with my account.
   • If you don't already have an account, make sure to Create a new account.
6. We'll email you a single use code. Enter your code and select Continue.
   • If you have more than one account, select the account you want to use and then Continue.
7. Choose either to chat with us or Have us call you.

You can also visit this link to know their supporting hours or get their number to ensure your connected to the right support: Contact QuickBooks Desktop support.

Once you've gathered all the data for your business, categorize it to keep everything organized and easy to reconcile. You can also review the troubleshooting steps to address the issues listed below for more information: Fix Web Connect import errors.

You're welcome to post again if you need further assistance with bank feeds. We're always here to help you.

@FAinc 

Do you run QB Desktop 2019?