I'm having the same issue. I download the transactions as a QBO file and when I try to import them I get "YOU ARE TRYING TO IMPORT A WEB CONNECT FILE WITH AN ACCOUNT TYPE THAT QUICKBOOKS DOES NOT SUPPORT. PLEASE CONTACT YOUR FINANCIAL INSTITUTION FOR DETAILS."
This manual import has worked for years. I'm on QB19. Also getting a microsoft.net framwork error message.
However, I AM able to import a QBO file from my bank. It seems that the chase website might be the problem.
Welcome and thank you for posting here in the Community. I'm here to help share information about uploading transactions using the web connect process.
@sullydews, I've checked and verified that we have reported issues with other users when trying to upload transactions using the web connect process in QuickBooks Dekstop (QBDT).
On the other hand, @mnsunderhill. We also receive issues when uploading web connect transactions in QuickBooks Online. As of now, I suggest importing your bank transactions using the Excel CSV files. You can check this article for the detailed instructions: How to import bank transactions using Excel CSV files.
You can also enter the transactions manually or use the direct connect.
We have already submitted a ticket about this issue and our engineers are all hands on deck working together with your bank to sort everything out. At this point, you may check this article about troubleshooting bank feeds web connect import issues and errors: Troubleshoot Bank Feeds Web Connect import issues and errors.
To receive resolution updates, I suggest contacting our QuickBooks Support Team to add you to the list of affected users.
To contact support:
Stay in touch if you have any other concerns, I'm always here to help. Have a great day to both of you!
Hello there, @Anonymous,
Thank you for joining this thread and bringing this to my attention here in the Community.
If you've already tried the steps outlined by my colleague, @Angelyn_T, and still having the same issue, I'd recommend reaching out to our QuickBooks Online Customer Care Team. By doing so, they'll be able to securely access your account and double-check why you're still receiving an error when uploading bank transactions using WebConnect.
Here's how to get their most up-to-date contact information:
After that, one of our specialists will take care of this and help fix your online banking concern.
Feel free to drop a comment below how the call goes, @Anonymous. Anytime you have questions or challenges while working in QuickBooks, please let me know. I'll be here to help. Take care always.
I am also having this issue. Just with Chase.com, not with my other web connects.
I am able to download the file but when I try to import into QB, I get the following error:
You are trying to upload the web connect file with an account type that Quickbooks does not support. Please contact your financial institution for details.
I am using Quickbooks Desktop Pro Plus 2018.
I am also having this issue as of last week. Quickbooks Desktop Pro Plus 2018. I get the following error only when importing the web connect file from from Chase.com:
"You are trying to upload the web connect file with an account type that Quickbooks does not support. Please contact your financial institution for details."
Hello there. mathspotswood.
I want you to get the best help possible.
QuickBooks only accept QBO files when uploading bank transactions using WebConnect. Since you're getting an error message, it's possible that you're using a file type which isn't supported in QuickBooks Desktop. (.QFX, .IIF, or .CVS).
In this case, I would recommend getting in touch with the Chase Bank. They have tools to investigate and verify your account type.
You may want to visit this article to learn more about the basic troubleshooting steps to resolve import error:Troubleshoot Bank Feeds Web Connect import issues and errors.
If there's anything else I can help you with, just let me know. I'll be here to keep helping.
Been having the same issue since last Friday and have called both Intuit and Chase. They show this as a reported issue and Intuit has an open investigation concerning this problem. Chase also shows this as reported issue and claims it has been escalated and they are working on it. Very frustrating...neither of them have a solution or work around at this time so I think we are stuck with manually entering transactions.
Hi there, @lrush.
Thank you for giving both Intuit and Chase a call to check on this issue. I'm here to share some information for how you can get your bank transactions imported in QuickBooks.
You can upload the bank transactions by performing one of the following workarounds:
• Import transactions using a CSV or other file type that is supported by QuickBooks.
• Use Direct Connect.
• Manually enter the transactions.
We received an update that using a CSV file will most likely import transactions successfully.
That should do it. Please give this a try and let me know how it goes. I’ll be on a look out for your response. Thank you for your patience. Take care!
Hi there, vicki7.
Thank you for joining this thread and letting us know that you're experiencing the same issue with Chase Bank.
We are currently communicating with Chase Bank to resolve the open investigation about uploading webconnect credit card transactions. I would love to add you on our list, but the security of your account is my top priority. Phone support has access and tools unavailable to me so that your information is kept secure and private.
I recommend giving them a call. By doing so, you'll be notified via email about the status of the investigation.
I'll also personally add a message on this thread once I receive updates.
Keep me posted on how the call goes. I'll be here if you have other concerns. Have a great day.
I've been for the last two weeks! I am a professional bookkeeper and it's not just a single incident. Whether I've been working on different clients on my own computer or if I've been on a client's computer on site I cannot download Chase credit card data to Quickbooks as a QBO file. I've tried every which way. It seems to be a global problem with the Chase site. I am able to download Chase bank data, but not credit card data. This is a serious problem. No one wants to enter things manually, especially if there are many, many transactions. One could export the data to a spreadsheet, format it correctly, and then import it to Quickbooks, but this also takes way more time than simply using WebConnect. I think Intuit needs to talk to Chase.
Hello there, @garydsisto.
Allow me to join the thread and help share additional information about the WebConnect issue with Chase Bank.
As mentioned above, our online banking team is currently working with Chase Bank to resolve the open investigation about uploading WebConnect transactions.
To receive resolution updates and to be added to the list of affected users, I suggest getting in touch with our QuickBooks Support Team. To contact support:
Thank you for your patience. We'll automatically add an update on this thread as soon as we receive updates from our online banking team.
As always, feel free to add a comment below if you have any other banking concerns. I'm always here to help!
I have spent the last 2 days on the phone with tech support with the same issue. Trying to get the last month or so imported before a tax appointment coming up.
The response I have received while have both Chase and Quickbooks on the phone was it was an issue with Quickbooks, but after a call today quickbooks is saying it is an issue with chase and they way they are exporting things. Chase has escalated it internally, but there is nothing that can be done until either one of them find a fix.
I am scheduled to receive an email with an update as soon as they get the issue fixed but they have no time frame on a fix.
Thanks for joining in this thread, garydsisto and sbarnesvta.
Let me share some updates about uploading WebConnect file from Chase into QuickBooks Online.
Our Engineering Team is still working diligently on a resolution. In the meantime, we’re asking for your patience and understanding while we’re continuing to fix on this. We’ll keep you posted on this thread as soon as an update is received.
We are actively working on a permanent solution and we should see a fix soon.
I'm always here if you need anything else in QuickBooks Online. Have a good one.
Okay, after some quick research I found a solution until QB and Chase can get it figured out.
Open the QBO file with a text editor (notepad).
Carefully scroll through the header until you find <INTU.BID>, the number after this should be 2340, i.e. <INTU.BID>2430. My bad Chase downloaded file had <INTU.BID>10898. I simply changed the 10898 to 2340 and re-saved the file. I checked all my older Chase files that have work in the past, and sure enough they all have 2340. After I replaced 10898 with 2340 it uploaded to QB 2018 pro just fine.
Thank you for letting us know what's happening and adding details in this post.
@arsurveyor, the workaround you've provided would be helpful to all affected users. Thank you for sharing that with us.
We're constantly communicating and working diligently with your bank to have this fixed in a timely manner. While I'm unable to provide a definite time frame for when this will be, rest assured that I’ll update the post once there’s progress.
I'd like to make sure your company details are added to the open investigation (INV- 24949) notification list. To do this, please contact our phone support.
That should assure you being added to our update list. Let me know if there's anything else I can help you with. Just add a comment below.
I tried this while on the phone with Tech Support, but the imports were not working correctly. Quickbooks would say it imported a certain number of transactions, but it was never the correct number. Sometimes it was only a single transaction and other times it was a few transactions, but it was never the correct number.
A bit more info, I just tried to download a new batch of web connect files from chase. When inspecting the files from a text editor it looks like they fixed the issue with <INTU.BID>2430 and it is being properly generated on the Chase end, BUT when you import the transactions it say" there is nothing to import".
So it looks like progress is being made but this needs to be fixed ASAP especially with everyone trying to wrap up last year before tax season.