Chase Credit Card QBO import fails

Tom19 · ‎January 21, 2019

Just upgraded from QB2015 to QB2019 since QBO files would not import!

After upgrade they still will not import.

I modified the checking account QBO file changing the <INTU.BID> from 10898 to 2430.

The checking account QBO file imported without errors.

I made the same change to the Credit Card QBO file which brought up the select account dialog and after selecting the existing account the Error Code:OL-222 was displayed.

I also tried the IIF download and that file was all errors.

Kristine Mae · ‎January 22, 2019

Hello there, Tom19.

There are reported issues about Chase .qbo file and IIF file. Some users are unable to import bank transactions. We have some troubleshooting steps that you'll have to perform. Please check these articles:

I also suggest reaching out to our QuickBooks Technical Support so you'll be added to the list of affected users. Here's how to contact them:

Open this link: https://help.quickbooks.intuit.com/en_US/contact.
Choose QuickBooks Desktop, then choose your Desktop version.
On the Contact Us page, click Solving Issues and Errors, then choose Common Errors.
Click either Get Phone Number or Start a Message.

If you have other questions, just drop a comment below.

Katr · ‎January 22, 2019

I'm having the same issue and I followed your instructions to be added to the list of affected users, and now the tech support suggestion was for me to invest in a support plan to fix this.

Anonymous · ‎January 22, 2019

Thanks reaching out to us today, Katr,

I want to make sure you're added to our notification list of affected users so you're updated about the importing issue with Chase.

The error you're getting requires account verification which we can't do in this public forum. While our engineers are continuing to implement a solution for this unexpected behavior, getting in touch with our QuickBooks Technical Support is the best option to complete your work.

There they can provide you additional workarounds and add your email to our live updates. However, you need to have an active Support Plan to get exclusive access with our experts. You may want to check this article to know more about our support policies: Intuit QuickBooks Desktop & Point-of-Sale software support policies

That should get you on the right track, Katr. Do let me know if you have any questions. Have a good one!

robert_dinero · ‎January 22, 2019

Hi,

Yes, I'm having this issue, too!

I use the Chase download activity feature for my accounts, by downloading the .QBO file, and then importing this file into Quickbooks Mac. However, as of one week ago, when I import the .QBO file for my credit card account Quickbooks crashes! (This issue is only happening with the CC account, checking and savings are importing fine.)

I researched this further, and determined that Chase has updated the .QBO format, and also introduced some errors. I compared with a previous .QBO file, and in the latest .QBO the date format is incorrect, as well as some other formatting differences. For example, please look at the tag <DTPOSTED>. The value (date format) as "01/16/2019" is incorrect. It should be something like [removed]00[0:GMT].

I edited the file, and when I changed to GMT format (as the previous version), the import works without issue.

HoneyLynn_G · ‎January 22, 2019

Good day, robert_dinero.

I appreciate you joining this thread and providing a workaround for the Chase Credit Card importing problem. I'm sure that other customers will find this helpful.

Of course, you can always drop by here in the Community for any questions you need help with. We're always here to help further. Have a wonderful day ahead!

Tom19 · ‎January 22, 2019

I discovered this problem myself since I had QBO files from 2017, so I wrote a C# program to read the QBO file and change all the dates on the <DTPOSTED> tag from MM/DD/YYYY to YYYYMMDD120000[0:GMT]. I also had to change the <ORG> and <INTU.BID> tags to the values in the 2017 QBO file.

naboolou · ‎January 23, 2019

Thank you for this information. I've been having this same issue with the Chase QBO file crashing Quickbooks.

I downloaded a test QBO of only a couple days worth of transactions to test this.

I changed the date format and the QBO file at least doesn't crash Quickbooks but I was then getting an error. I updated the FID and INTU.BID to 2430 for Chase as someone else recommended and that fixed the error.

However, the problem I have now is that only the first transaction from the QBO is imported out of around 10 or so. I'm not sure what is causing this.

Eli3 · ‎January 23, 2019

I'm having the same issue applying my Chase business credit cards .QBO files to QB 2017. I've hacked the .QBO applying the same <INTU.BID> as before and updated the DTPOSTED entries as mentioned.

However, I'm getting an OL-222 error now.

One thing I did notice different from the working file and the non-working file is that all of the transactions are now missing their FITID information. It looks like it starts with a YYYYMMDD normally, but I'm not able to decode the rest of it.

Anonymous · ‎January 23, 2019

Thanks for joining the conversation, Eli3,

I can share an update about the OL-222 error when importing .QBO files in QuickBooks.

This issue is recently tagged this as an ongoing issue by our Support Team. They're already investigating the cause of this hurdle and are working to implement a solution . While they do, I'd recommend getting in touch with our QuickBooks Desktop Support so you're added to our notification lists of affected users.

There they can provide you additional workarounds to complete your work temporarily. Here's how you can get them:

Open this link: https://help.quickbooks.intuit.com/en_US/contact.
Select QuickBooks Desktop.
Choose your QuickBooks Desktop version.
Click on the Solving Issues & Error Messages menu then select Common Errors.
Scroll down and click either Get Phone Number or Start a Message button.

That should get you on the right track, Eli3. You can have our representatives add you to the investigation number INV-24949. Once added, you'll receive live notifications when an update is available.

Please notify me if you need QuickBooks assistance. I'll be glad to help whenever you needed me. Have a good one!

Sheri · ‎January 24, 2019

Starting last week my Chase credit card transactions could not be downloaded - just the checking account transactions. I called Chase and they tried to explain to me that the main online user needed to grant access. It was not really clear what they meant, but I did a search on their website this morning and found this:

Search results

You asked: "quickbooks"

To activate financial management software like Quicken® and QuickBooks® (and let it access your Chase accounts), go to the person icon in the upper-right and choose "AccountSafeSM," then choose "Desktop Apps" from the menu. Choose "Continue" and then "Set it up" to connect the software to your Chase accounts.

I am not sure if this works or not since the business owner is out of the office today so I can't try it.

Anonymous · ‎January 24, 2019

Hi there, @Sheri.

Thank you for sharing this on the Community page.

Since these steps were from the Chase website, I'd suggest contacting them again to verify if you can proceed in following this process. They can further assist you in going through the steps.

Please don't hesitate to let us know how it goes. I'll be here if you have other questions. All the best.

vicki7 · ‎January 25, 2019

I am also unable to import my Chae web connect into QB Desktop ( i recently upgraded to v 2019), it says the type of account isnt supported... when I click on the Web connect file, it automatically opens QB 2018.. which is not where my file is located (I have multiple versions because yes I am an accountant and have clients in mutiple versions, I test the newest QB desktop version on my own data file to make sure it is working.... may I just say there have been many issues with this version.... This web connect failure is really bad... please add me... to whatever list... so I can get this fixed ASAP YESTERDAY please!

MirriamM · ‎January 25, 2019

Appreciate your time raising this to our attention, vicki7,

Our engineering team are currently working on a resolution. At this point, we will need to wait for an update on the ticket that we have submitted about this issue.

In line with this, I also invite you contacting our QuickBooks Customer Care support. They can add you to our notification list so you can stay updated. You can follow the steps above provided by my colleague on how to contact support.

Thanks for your patience as we continue working toward a resolution.

Keep me posted if you have further questions, I'm always here to help. Have a great day!

robert_dinero · ‎January 28, 2019

Hi all,

Here's an update on the issue:

Today I noticed Intuit have added an error message when importing a .QBO file to CC accounts, instead of just crashing QB (attached image).

At least this is some progress, but it does not fix the issue.

Intuit, when will this issue be fixed? We cannot import data into CC accounts, and this is important for filing taxes, etc. Today begins the official tax filing season.

Kristine Mae · ‎January 28, 2019

Good day, Robert_dinero.

We're unable to provide a specific time frame to when this will be fixed. Rest assured, we're working with your financial institution to get this issue fixed as soon as we can.

You can use the IIF file to download transactions to QuickBooks. We use this file to import and export lists or transactions to and from different platforms. Please check these articles for more information:

If you haven't called our technical support yet, please reach out to them. This way, you'll be added to the list of affected users and you'll get notified once a fix is applied. You can get the steps on how to contact us from my friend @Jen_D's post.

You can always go back to this thread if you have further questions.

sfvaughan · ‎January 31, 2019

I just contacted QB and was told that there was no workaround and that all Chase transactions would need to be entered manually. So.....instead of 15 minutes, just plan on spending 5-7 hours...but hey, nobody has much to do this time of year do they?

Anonymous · ‎January 31, 2019

Hello susanna,

Our engineers are working with the bank to fix the issue. While we're waiting, we encourage you to manually upload bank transactions using a CSV Excel file. Please check out this article: How to Import Bank Transactions Using Excel CSV Files.

Thank you for posting.

Ckraimer · ‎February 02, 2019

I'm glad to hear Intuit is working directly with Chase. They have dropped the FITID identifier completely and restoring it is the only way this is going to work again. I thought about calling, but didn't want to try to get that info to the right person, never going to happen.

Anonymous · ‎February 02, 2019

Thanks for dropping by, Ckraimer.

We’ll keep an eye on their investigation about this issue and will let you know in this thread once there are updates.

Please continue on posting here if you have other concerns about QuickBooks.

DryHeat · ‎February 04, 2019

I'm having the same problem with downloading .qbo files from Chase. The older files have <FITID>[removed][removed]804 new files have <FITID>NONE. I manually edited the file so <FITID> had a unique identifier for each transaction and I was able to import into QB. Next step will be to write VB code to automatically update <FITID> with unique ID.

HoneyLynn_G · ‎February 04, 2019

Hello there, @DryHeat.

Thank you for joining this thread and providing us a workaround.

The Chase bank .qbo file format has changed resulting in being unable to directly upload the file within QuickBooks. We're diligently working to ensure a seamless connection between your bank and QuickBooks. For now, manually editing the file is the available workaround.

I'd also suggest for you to reach out to our Customer Care Team so you will be added to the affected user's list. Rest assured, we will send you an email notification as soon as this issue is rectified.

Go to https://help.quickbooks.intuit.com/en_US/contactus.
Select your QuickBooks product.
Select a topic.
Click the Get Phone Number button to see the support number.

Should you need any additional assistance while managing your bank transactions, you can leave a comment below. I'll be sure to get back to you.

robert_dinero · ‎February 05, 2019

Hi all,

Here's another update:

It seems the issue has morphed. The QBO now imports without crashing Quickbooks (Mac Desktop). However, nothing is actually being imported, even though there is lots of data that should be imported (it's been almost a month).

There are numerous hacks, and workarounds out there that suggest editing some of the values and tags the QBO file. This might work in certain cases, however, it's not a real long-term sustainable solution.

Also, none of the responses here from Intuit are helpful. Sorry QB team :( When will this be completely fixed?

robert_dinero · ‎February 05, 2019

Hi all,
Here's another update:
The QBO now imports without crashing Quickbooks (Mac Desktop). However, it doesn't actually import anything even thought there is a lot of data that should be imported.
There are a few workarounds that have been suggested out there, i.e. editing some of the tags, and values in the QBO file. This might work for some situations, however, it is not a long-term sustainable solution.

QB team, when will this be fixed completely?

Kristine Mae · ‎February 05, 2019

Good day, Robert_dinero.

You don't have to apologize. As much as possible, we don't want to see our customers inconvenienced. We are always striving to create a positive customer experience.

Regarding your concern, we've been partnering with Chase to help find a solution. And, they're planning to release a fix this week.

Keep in touch if you need our help. We're always here for you.

Topics

Training

Community

Resources

Chase Credit Card QBO import fails