Hi there, @jackie4.
Thanks for reaching out to us here in the Community. I'm here to share some information about the error you're getting in QuickBooks Online (QBO).
This has been reported as an ongoing issue with an investigation number INV-25020 and our product engineers are diligently working to get it fixed as possible. You can try to manually enter the transactions or import them as a CSV file as a workaround.
1. Go to Banking menu at the left panel, then Banking.
2. Select File upload from the Update drop-down.
3. Click Browse and choose the file you downloaded from your bank, then Next.
4. From the QuickBooks Account drop-down list, pick the appropriate bank or credit card account and Next.
5. Map the statement fields according to your CSV file format and select Next, then select the checkboxes of the transactions to import and Next again.
6. When prompted whether you want to import now, choose Yes, then Let’s go when the Import Completed.
You can also refer to this article for more information: How to import bank transactions using Excel CSV files.
While we don't have an exact time frame as to when this will be fixed, I suggest contacting our Phone Support team so they can add your company details to the list of affected users. You'll be notified via email when there are updates available. Here's how to reach them:
2. Choose your QuickBooks product at the upper right.
3. Select a topic.
4. Click on the green button that says Get Phone Number.
That should answer your concern for today. Thanks for your understanding and patience while we look into this. I'm only a few clicks away if you have any follow-up questions. Take care always.
You might want to try checking the update about this issue that I've provided above.
Should you have any additional questions or concern, don't hesitate to leave a comment below so I can get back to your right away. Have a great rest of the day.
We are also having an issue uploading a QBO file to Quickbooks desktop.
We prefer not to use a csv file with mapping...too much room for error.
We wold prefer direct link from the software.
Note: of the banks we use, only Chase is unable to process the download (again issues with Chase Bank and Quickbooks interactions)
Fritz...here is what happened when I tried to get chat support for this problem. (see below chat) QB's support staff are not knowledgable at all. I truly don't know how QB's stays in business.
Please add me to your list for support on this very problematic issue.
Hello there, @ChicagoCFO.
Thank you for joining this thread. I'm here to help share some information about this error message.
At this time, our Engineering Team is still working to get this fixed. If Importing a CSV or other file type supported by QBO is not ideal for you, you can try to manually enter the transactions as suggested by my colleague @FritzF.
I appreciate you telling us about what happened @BLP. I can pass along all the feedback you have to the appropriate channels and make sure your concerns are addressed accordingly.
I'd still recommend contacting our Online Payroll support so they can add you to the list of affected users. They'll be able to access your account in a secure environment and in the meantime they can suggest other workarounds for you to try.
Here's how to get their contact information:
I'll be here to give you an update once the issue is resolved. Let me know if you need anything else.
Hi there, TMiller,
Thanks for reaching out. We are continuing our investigations to determine the root cause of the issue.
For the meantime, we will need to wait for an update on the ticket that we have submitted about this issue. As soon as we hear anything from our investiagtions team, We will reach out to you and provide an update.
If there's anything else you need help with, please feel free to reach back out. Have a great day!
Hi there, @ChicagoCFO.
Thanks for coming back to the Online Community and letting us know the file type used to download transactions from Chase bank.
Information like this will help other users who may be experiencing the same issue.
You can post anytime if you have questions or want to share your best practices using the product. Please know the Community has your back.
The file extension of the file downloaded from Chase in my case is QBO as it should be. OFX is not an option in the dropdown at Chase. Interestingly, though, this problem with QBO being unable to upload the file started a few days ago when CHASE made an improvement to their "Download Account Activity" section. Previously, the CHASE website would get "stuck" when attempting to load the "Download Account Activity" page. I had to use the "reload page" button to reload it, then it worked. Now, the page loads correctly the first time and I notice there are more options concerning how much activity the user wants to download. And the resulting file will not load to Quickbooks Online.
We've received an update from our engineers about this issue, TMiller.
After further research, it appears that the .QBO file type is invalid when downloading transactions from the Chase bank. This file type that Chase used to offer does not match up with our sample files. I'd suggest checking with your bank for other file types which are compatible with QuickBooks Online.
You can also contact us to help you upload the transactions into QBO.
Here's how to get our contact number:
I'll be around if you need anything else.
Quickbooks Online has this instruction when uploading transactions:
Chase offers these file types for data download:
QFX - QUICKEN Web Connect
QIF - Quicken or Microsoft Money
IIF - Quickbooks
QBO - QuickBooks Web Connect
Excel, CSV - Spreadsheet
Are you saying that Chase's QBO file has been reformatted and no longer works with Quickbooks Online?
As I copied from the Quickbooks Online uploading instructions, are you saying that QFX which is defined by Chase as being for QUICKEN should load to Quickbooks Online?
Why are Chase and Intuit not working together to fix this?
Allow me to give you the accepted format types for uploading files in QuickBooks and help you successfully upload them.
Here's a list of the accepted files types:
Meaning, you can use your Chase QFX file to upload it in QBO. Here's how:
Read this article for more information: How to Upload More Than 90 Days of Bank Transactions?
Also, Intuit is working together with Chase to fix issues that users encounter to improve their experience using the product.
Feel free to leave a comment below or post again if you have other questions.
I found that neither the QBO nor the QFX extensions worked for Chase (the QBO extension worked previously - last month). Only the CSV extension worked, albiet with the extra step of some basic mapping, it worked similar to the QBO file in prior months.
Hello there, bknsf.
Thanks for informing us that neither the QBO nor the QFX extensions worked. I want to ensure you’ll be able to download transactions seamlessly.
Just to clarify, did you get any error messages/codes? Have you tried checking the mapping and settings of your transactions?
I appreciate any details you can provide. I'll be on the lookout for your reply.
I've had this exact issue come up today as well. I have two separate employee cards for the same chase account. At first, both cards were downloading into QBO perfectly. But, one day, only one card downloaded while the other I had to manually input by downloading the QBO file from Chase.
Now that I'm getting this error, it would require me to input the many dozens of transactions every week. Help! Please get this fixed. It's been many months already.
Following the thread above, it has been verified that it's the invalid file type causing this error.
If you've verified the correct file type and you're still getting the same error, please give us a call. This way, our engineers will reopen the case and work on the fix.
Please @SophaAnnL to get our contact number.
Always reply to this thread anytime if you have other concerns.
I've had the same problem with employee cards at Chase for months. I talked to both Intuit and Chase multiple times. The bottom line given by Intuit is that it will NEVER work again as it did before. I.e. automatically load all employee cards together in one file from Chase into QBO to a single Account in the Chart of Accounts. I don't think Chase OR Intuit understands the issue. The single credit card file from Chase that contains all of the employee cards and transactions is not shown as one available when attempting to set up the automatic feed into QBO. BUT the desired file IS the one available for manually downloading from the Chase website. I don't understand why Chase and Intuit cannot talk to each other directly to work this out. Chase claims they do not support their side of the ability to automatically load the banking data into QBO. How can that be when they obviously provide the list of accounts/files available for linking to QBO!
I have been left with manually downloading the file from Chase and manually uploading into QBO and now that doesn't work either!
Yes, I'm very frustrated with Intuit and Chase through all of this. I don't have this problem with Capital One!
Hello there, TMiller.
I appreciate you for sharing the result of your interaction with both Intuit and Chase Bank. This isn't the kind of service we want you to experience.
At the moment, our product team is still currently working with the Chase Bank so they could come up with a permanent fix. Since you've already communicated with our QuickBooks Care Team, rest assured you'll be receiving the latest updates about this investigation.
We will also make sure to update you and other users affected once we receive any progress of this current investigation.
I appreciate your patience while we continue working with this. Should there'll be anything else you need, just let me know and I'll get back to you.
Yes, I have been having same issue for more than 7 days now. No matter how complex the issue can be, it is not reasonable to take so long to fix, especially considering it was working before. I have talked to QBO and Chase and both are "working diligently on matter". Honestly, diligent work would have generated a fix.
I cannot import with CSV since it risks generating duplicities and selecting manually, for many cards and many employees, is a HUGE manual labor.
We need this fixed immediately before month closing!!