OL-222 Error

Utilize the trial version of this app to isolate the issue. If the same error persists, your bank is the problem.

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

Thank you, I just did this. It downloaded my statement in .csv format. 

There were these two errors at the bottom

Unexpected OFX  I/O Exception

Unexpected EOF

Thanks,

Melissa Corey

Hello @mistymossy, thanks for getting back to us.

In QuickBooks Desktop, we can only download the Web Connect file using (.qbo file). Since you've downloaded your statement in .csv format, that's the reason why there are two errors appear at the bottom. With that, make sure to use the .qbo file extension so you can open the downloaded transactions.

When importing your transactions into QuickBooks, you'll have to create a backup of your company file to have a secured copy of your data. Once done, you can follow the steps above.

1. Sign in to your bank's website and find and download the Web Connect file .qbo file.
2. Open QuickBooks and your company file.
3. Follow the steps to import the .qbo file.

As Fiat Lux - ASIA suggested, if you still can’t open the .qbo file in QuickBooks, there might be a problem with your bank. You'll need to contact your bank’s support for help.

If there's a need to refresh the connection with your bank soon, you can check these articles for more insights:

• File types and extensions used by QuickBooks Desktop.
• Learn how to fix some of the OL and OLSU Bank Feeds errors in QuickBooks Desktop.

Please go back here if you have other questions. Take care and stay safe always.

Thanks for the reply. To clarify, the moneythumb program converted my .qbo file to csv. 

I have already downloaded the .qbo file. My credit card company says to contact qb. 

It’s a big circle of the same help tips without anything actually working. 

I

Thank you for this very detailed post. I'll provide the steps you need to take, so you can get help on this matter, @macc.

The Error OL-222 that you get means QuickBooks didn't receive a valid response from the financial institution's server. This is often caused by when you try to import one or more characters .QBO file that isn't compliant with the Open Financial Exchange (OFX) standard for exchanging financial data with QuickBooks.

Before we do any troubleshooting steps, I'd recommend creating a backup copy of your company file and updating your QuickBooks Desktop release version.

Aside from not receiving a valid response from the financial institution's server, unsupported characters in the .QBO file can also cause this error. Here's how we can edit the file:

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.

You can also use Excel to edit the .QBO file and search for a QBO to CSV converter online. 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 the same thing happens, I'd recommend reaching out to our Technical Support Team. They can review your file and ensure you can import the banking transactions. Here's how to reach them:

1. Click Help at the top menu and select QuickBooks Desktop Help.
2. In the Have a Question? window, select Contact Us.
3. Go to the first section and enter the details of your concern.
4. Click Search and move to the second section.
5. Click Start a message. 

I'm also adding this article about our contact options and support available for your reference: Contact QuickBooks Desktop support.

In case you encounter similar bank feed errors in the future, keep this article for your reference: Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop.

Should you have questions or other concerns, please let me know. I'd be sure to jump in as soon as I can. Take good care.

If facing issues while bank synchronization, Follow this to fix QuickBooks Error Code OL 222.

Thank you for the reply. I did this and searched for &amp and it is not in the file. Can you please let me know what other text I can look for that may be the culprit? I did verify the code for the institution is correct. Thanks again.  

Thank you. I haven’t tried the FIDIR yet. I will do that. 

I appreciate your time getting back in here, @mistymossy. Let me chime in and add some details about correcting invalid formatting that caused the error. 

An example of invalid characters would be &. If this is not on the file, I suggest following the steps in downloading a new FIDER.txt file. Take note that before doing the steps, make sure to back up your company file and close your QuickBooks. 

For detailed steps, feel free to open this article and proceed to Solution 3:  Error: OL-222 after downloading a Web Connect file from an approved bank.

Once everything is set, you can import the file again to QuickBooks Desktop.

Additionally, I'll be sharing this link on how to add and match Bank Feed transactions in QuickBooks Desktop.

Please get back to me if you continue to get the same results so I can look further into this. Keep safe and have a good one!

Rubielyn,

Thanks. 

I’m going to try the fidr fix. I’m getting a little confused. My QB is closed. While holding ctrl, am I clicking on my QB app on my computer? I can’t seem to get past the screen that shows opening a company file. 

Thanks. 

I did search my computer for fidr.txt and didn’t see it. I know my credit company needs me to manually load the file and then import it. 

Thank you every one for bearing with me thru this.

I followed the instructions in this link to update my fidir file.

https://quickbooks.intuit.com/learn-support/en-us/bank-feeds/update-the-financial-institutions-direc...

I still get the OL-222. I appreciate the help. 

Let's make sure that you'll be able to get past this error, macc.

Generally, there are several factors why you're getting this error. You may be using an outdated version of Internet Explorer, there may have problems with your bank accounts or your bank may have changed their service offering to Web or Direct Connect. Since you have already performed some series of troubleshooting steps, I recommend getting in touch with our support team to check what's causing the error. They have additional tools to verify if this is caused by some unusual responses or behavior.

For your reference, I've also added these articles for your guide: 

• Error OL-200, OL-202, OL-206, or OL-226: Your last online connection was not completed
• Get help with error OL 301 or 393
• Error OLSU-1024 or OLSU-1022 when creating an account for Bank Feeds
  
  

Please let me know if there's anything else that you need help with with your bank feeds. I'll always make sure to get back.

I redid the download to this trial moneythumb. I did not get the error. It loaded all of the transactions

Then says

Unexpexted OFX/IO exception

Unexpected EOF

10 transactions processed.

Thanks

1. Hello,

I thought I would give this another try. I am getting the same error. I was able to view my connect log and it says, Not all fields present. Bankturnlist missing tag: DTSTART.

I have opened in note pad and am not sure where or how to format this. Can you help?

Thanks

Thanks for getting back with the Community, macc.

Since you're still receiving errors after performing our recommended troubleshooting processes, I'd recommend getting in touch with our Customer Care team. They'll be able to pull up your account in a secure environment, conduct further research with you, and create an investigation ticket if necessary.

They can be reached while you're using QuickBooks.

Here's how:

1. In your top menu bar, go to Help, then QuickBooks Desktop Help.
2. Click Contact Us.
   
3. Enter a brief description of the issue in our Ask a question (or tell us what's wrong) field.
   
4. Hit Continue.
   
5. Select We’ll contact you for a callback or Message Us to start an instant messaging session.

Be sure to review their support hours so you'll know when agents are available.

I'll be here to help if there's any questions. Have a lovely day!

Thanks for the reply. I was able to open the qbo file with moneythumb correctly. What does this mean?

Thanks, I have already tried to deal with qb support. 

I used moneythumb and the file opened properly. What does this mean?

@mistymossy  I have what I think is a somewhat definitive answer, based on some troubleshooting I did for a customer.

We offer several tools that create OFX/QBO/QFX files, including the  BRC Excel to OFX/QFX/QBO Converter , BRC QIF to OFX/QFX/QBO Converter and the BRC OFX Cleaner .

A customer of ours using the Excel to OFX Converter upgraded to the latest release and then got an OL-222 error. They assumed it was something to do with the upgrade. Instead, though, it had to do with the contents of the file, which QuickBooks was choking on - incorrectly.

It appears that when QuickBooks can't parse the OFX file according to the OFX standard, it will issue an OL-222 error. In hind-site, this may be the only trigger for this particular error, given the history of cases I can remember over time.

In my customer's case, the OFX file is valid, but QuickBooks is parsing the file and then applying various rules in the wrong order. 

I checked its validity using the OFX File Analyzer, published by Microsoft, which is very picky and very closely follows the OFX standard. The OFX standard was created by Microsoft, Intuit, and CheckFree. And then Intuit immediately bastardized it and created the QFX and QBO sub-file formats so they could charge banks to connect to Quicken and QuickBooks. Nice, huh?

My customer's file passed the OFX File Analyzer with flying colors, so I decided to find out what QuickBooks thought was wrong with the file.

After some testing I realized that QuickBooks is testing the length of various fields against the OFX standard maximum lengths before it is decoding the text to revert it to the original length. It is important to decode the text first, because the escape encoding replaces one character with up to 6 characters, making the text much longer.

Many characters must be encoded in this way in OFX files including ampersands (&) and many high-ascii character like those used in various European languages. ASCII characters with numeric values smaller than 32 and larger than 127 have to be encoded.

For example, consider this made-up name, which is 35 characters long:

Renéaldo Lacért Schönenfeld Limited

The <NAME> field in the OFX standard has a (rather ridiculous) field length limit of 32 characters. So, the name must be truncated:

Renéaldo Lacért Schönenfeld Limi

Then the special characters é and ö have to be encoded, where 233 and 246 are the ASCII numbers for the characters. Added to the OFX file, the name will (correctly) look like this:

Ren&#233;aldo Lac&#233;rt Sch&#246;nenfeld Limi

When processing the file, QuickBooks should decode the <NAME> before testing the length, but it does not. Instead, it tests the length first and then issues an OL-222 error. At the same time, most other OFX enabled apps work just fine, including the parser mentioned above, because they actually follow the rules.

There was a suggestion on this thread by Intuit that encoding like this is not supported, but that is incorrect.  QuickBooks handles it just fine in cases where the name added to the file with encoding is shorter than the max length. For example, this will work just fine, because it is only 25 characters long:

Ren&#233;aldo Lac&#233;rt

After importing, the name will look like it should:

Renéaldo Lacért

Escape character sequences include:

&amp;  for "&"

&lt;  for "<"  

&gt;  for ">"

and &#ASCIIID;  for ASCII characters 1 through 31 AND 128 and on up.

You can see the characters and number values here: https://ascii.cl/htmlcodes.htm

So, if the file you're working with contains any of these escape character sequences, and the resulting encoded field length is longer than what is allowed, and QuickBooks is choking, then the banks are right: This is Intuit's fault for writing buggy code.

The only solution, until Intuit fixes QuickBooks (don't hold your breath), is to edit the OFX/QBO file using a text editor and shorten the fields so they pass the length test with the encoding, or remove the encoded characters completely, which will make the remaining text short enough.

Both the <MEMO> and <NAME> field max lengths are 32 characters.

Thanks. So, I downloaded my credit card file and saved as text, analyzed with the program.

This is the error that showed

*** All line number references do not include header lines ***
***OFX 1.02 Add ~10
***OFX 2.0 Add ~2
Running Data Through Parser
HRESULT = 0
Error Code = 0

HRESULT = -2147450874
Error Code = 1
Severity = X
Type = C
Error Message = XC%s element not allowed at this point in %s element
Other Info = MNYSGMPB: SGML error at (null), line 31 at ">":
XCSTMTTRN element not allowed at this point in BANKTRANLIST element

Do you know what this means? and thank you so much.