Has this issue been fixed yet? 

Thanks for joining this thread, @Gourmet Mommies.

We'd like to ask you a few questions to understand your situation better and provide the best possible assistance. 

First, can you please let us know which bank you're having an issue with? Also, have you encountered any errors? If so, I'd appreciate it if you can share a screenshot of the error message.

We're looking forward to your response. 

Please feel free to click the Reply button. We're here to help.

This has been an ongoing Chase issue since the update several month ago. I added myself to the open investigation and haven't heard anything since. Intuit continues to make changes (new and shiny, but not helpful usually) but does not address actual ISSUES. We shouldn't HAVE to use work arounds. Do they Beta test anything EVER?

I no longer work for clients that bank with Chase and will not take on any new clients that do since QB doesn't seem to want to fix this.  They put the blame on Chase.  Which to be fair is accurate, this issue came about when Chase did a system update.  However, QB should be working with Chase to resolve and shouldn't have to ask us users what the issues are.  

No and it's my understanding that it will not be fixed.  I received a reply that the problem was with Chase's security udpate.  Chase doesn't share the necessary information with QBO any longer.  I was told to contact Chase to resolve the problem.

No and it's my understanding that it will not be fixed.  I received a reply that the problem was with Chase's security udpate.  Chase doesn't share the necessary information with QBO any longer.  I was told to contact Chase to resolve the problem. @Gourmet Mommies 

I appreciate you for replying to this thread, @sooverit2. I understand the inconvenience this has caused on your end. 

Let me share some insights about QuickBooks Beta testing to enlighten you. QuickBooks always does Beta testing before releasing an update to each product. Our engineering team also hears the feedback of our customers including some features that can help for a better experience.

Regarding your issue, QuickBooks doesn't do beta testing because the update is coming from your bank. QB only depends on the shared information coming from your bank. It is your bank that hides the information that you need.

Furthermore, let me provide this article for your reference about common errors of importing bank transactions: Common errors for importing bank transactions using CSV.

Drop a reply below if you have more questions about beta testing and other QuickBooks-related concerns. We'll be here to help.

I was referencing Beta Testing in regards to the "New and Shiny" features or updates. Not the Chase issue. The Chase issue seems like it can only be fixed between Intuit and Chase. Contacting Chase from our end will not do a thing. 

I believe I found a fix to this. After months of ongoing back and forth between Chase and Quickbooks, I decided to try disconnecting my bank feeds from Chase to Quickbooks and I downloaded a small range date for each of my previous connected accounts for two day time frame. I uploaded each CSV file to QuickBooks. Once I saw the transactions displaying with numbers and not XXX.. I then "Excluded" the transactions as they were duplicates, however after I excluded them I reconnected the automatic bank feed for transactions to show automatically, and FINALLY!!!!! As the transactions have been populating in each day, I no longer see XXX anymore. This has been processing normally for 2 weeks now without any problems! 

See the attachment for proof! I hope this helps everyone who has been as frustrated as I've been for months!

Impressive work!  Thank you for sharing and doing what QB was unable to provide.... a resolution!

Has anyone else tried this? I have many clients using Chase Bank, but most of the time it requires two-step authentication to reconnect the bank feed - And that is "herding cats." I don't want to try this unless others have tried and verified that it works.

Same here. Only my clients with Chase accounts are having this issue and it makes it impossible to know if certain transactions are payments or distributions to personal. Annoying to have to wait until getting the physical bank statements. Really defeats the purpose of the bank feed to be honest. I am going to call Chase and threaten closing my accounts and recommending the same to all of my clients if they don't fix this. The reason provided by QBO that they are doing it for security protocol does not make any sense, as there is absolutely no sensitive data in any of these descriptions.

Having the same issue with QBO. Bank with Wells Fargo and this is not an issue on either bank's end. This is an issue with Quickbooks. Has anyone found a solution that doesn't involve doing way more work? This essentially makes creating rules impossible. The whole point of having rules is to NOT have to manually input each transaction. I will not continue using this expensive software if there is no solution that doesn't involve doing significantly more work. There is no advantage at that point.

Hi there @JProp.

I understand that you have been facing some challenges with QuickBooks (QBO), and I'm here to help you resolve this issue. Since you have me, I will share a workaround to complete your task and enable you to utilize the program. This can help in aiding your task and enable you to use the available features of the program. However, I would also recommend you get in touch with our Customer Care Team, who can assign a representative to assist you with the process. They will also investigate if the issue is related to compatibility between the program and the operating system. Here are the steps you can follow to get started:

Contact Support

1. Sign in to your QuickBooks Online company.
2. Select Help (?).
3. Select either tab to get started:

• Assistant: Get quick, personalized answers. Select a suggested option or type a question or topic you need help with. If you decide you need further help, you can still Talk to a human.
• Search: Search the QuickBooks Online knowledge base directly, or select Contact Us and choose a way to connect with us:
  • Start a chat with a support expert.
  • Get a call back from the next available expert.
  • Ask the community to get help from businesses like yours.

You can also check this article for more details and be sure to review their Support hours to know when agents are available.

In addition, if you want to connect your bank and credit card accounts, QuickBooks can automatically download transactions up to a specific date. However, if you want to enter older transactions, or if your bank or credit card can't connect to QuickBooks, you can still upload transactions manually. You can refer to this article for more information: Manually upload transactions into QuickBooks Online

Please don't hesitate to ask follow-up questions or submit new ones if you need anything else. The Community is always ready to help you all the time.

The only thing that allowed the bank rules to work when the information is missing from the Bank Feeds is to ignore the Bank Feed items, download a CSV from the bank, and then import it into QBO.  The banking detail that we are accustomed to seeing was in the CSV information for Chase.  It was a little extra work but far less than opening the checking account or statement and looking up each individual transaction to manually process.  My Chase bank feeds did eventually start working again.  I had the client do an update with their owner login credentials and it seemed to start working shortly after.

I had my affected clients sign on and update the bank feeds with their owner credentials (with the bank log in) and the feeds started working as they should again.