Skip to main content

Get 50% OFF QuickBooks for 3 months*

Buy now
Switch to QuickBooks and 70% off for 3 Months
Talk to Sales: 877-683-3280
Hours
Mon - Fri, 5am - 6pm PST
Sat - Sun, 7am - 4pm PST
Product support & help
Need help signing in?
K
knapiks
September 22, 2021
Question

error OL 222

  • September 22, 2021
  • 3 replies
  • 1 view

When trying to import transactions from Suntrust I am getting error code OL 222 for one of the accounts.  I have googled an d read and tried everything.  What do I need to do to get these transactions into QBs?  Can I import a csv?  If not - what?

3 replies

Fiat Lux - ASIA
Fiat Lux - ASIA
Level 14
September 22, 2021

You may need a converter app.

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

 

C
Charies_M
Level 9
September 22, 2021

Let's get rid of the error so you can import transactions successfully, knapiks.

 

The Error OL-222 you're getting means QuickBooks didn't receive a valid response from the financial institution's server. This happens when you try to import one or more characters. 

 

You'll want to correct the unsupported characters in the .QBO file which causes this error:

  1. Right-click the .QBO file and select Edit.
  2. Select any text editor app to open the file.
  3. Find and remove &amp from the text as it is an invalid character.
  4. Save the file again.

Visit this article for more details on how to fix the Error OL 222 in QuickBooks Desktop: Error: OL-222 after downloading a Web Connect file from an approved bank.

l

Otherwise, use Excel to edit the .QBO file and search for a QBO to CSV converter online. (Like the one Fiat Lux - Asia suggested) After editing the file, make sure to convert it back to .QBO file format.

 

Once done, you can import the file again to QuickBooks Desktop.

 

If you need other helpful articles in the future, you can always visit our site: Help articles for QuickBooks Desktop.

 

Anything else you need help with can be answered here in the Community. Just let me know and I'd be happy to assist. Have a good one.

Fiat Lux - ASIA
Fiat Lux - ASIA
Level 14
November 15, 2021

Wow, this is so typical of QB support. I had this same issue like 8 years ago before I trashed it. I've recently been forced to return to desktop due to the outrageous costs of QB online, and still the same issue exists now as it did then. My first online download failed, same stupid, nonsensical, error message, which pretty much says "f*** you, we don't care enough to actually fix this or tell you what's wrong with the file."

 

Thanks a pantload QB support. WTF did I pay for - the same piece of crap from 8+ years ago? really?

 

What you're actually telling us is that we need to just ignore the massively broken download/sync and manually enter everything - like any of us have time for that. Nice.

 

Intuit still sucks.


@zog wrote:

What you're actually telling us is that we need to just ignore the massively broken download/sync and manually enter everything - like any of us have time for that. Nice.

 

@zog 

Consider to use the converter tool to import your data as a workaround.

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

 

Otherwise, time to explore other accounting apps to migrate your data.

R
Rocha corporation
April 5, 2022

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.

    JasroV
    JasroV
    Level 8
    April 5, 2022

    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!

    F
    From The Field Catnip
    May 21, 2022

    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,

     

      D
      DaveThomas2
      July 1, 2022

      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.

      LieraMarie_A
      LieraMarie_A
      Level 8
      July 1, 2022

      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!

      Need QuickBooks guidance?
      Log in to access expert advice and community support instantly.
      Terms & ConditionsAccessibility statement