In Desktop Pro 2019, since October of 2018, chequing data from RBC has not been importable through the webconnect application. This is 6 months without this function operating properly. QB told me several times that it is the fault of the Bank but through several calls (conference with QB and RBC on the same call) it is now in QB hands to deal with as it only happens with certain QB program versions. Can we please get this escalated and fixed?? This is super frustrating and I don't want to enter things manually.
Thanks for reaching about. I know this is taking longer than usual to fix and I appreciate your patience. I acknowledge that your time is valuable and it's important you continue entering transactions manually as you've been. If you need help with doing that, please don't hesitate to reach out. In the meantime, I'll pass your feedback to our engineers and express to them how expediting this process would make things easier.
Let me know if you have questions. I'm here to help.
I appreciate the sentiments James. The issue is that I've been waiting for the software to be fixed as I thought it couldn't take more than a month to figure out (my own discretion of course) and now I have a bunch of entries to make.
I appreciate you passing along the sentiments to the engineers as I'm sure it's not just me in this scenario.
I appreciate your time for joining this thread and for sharing your experience about this issue.
Errors like this occurs when the financial institution was not able to response to QuickBooks server. We can try to update QuickBooks to the latest release to fix the issue. Though, if it didn’t work, you can follow the second and third solutions provided in this article: https://quickbooks.intuit.com/community/Banking-and-bank-feeds/Error-OL-222-after-downloading-a-Web-...
If you’re continue to experience the issue after following the article, I’d recommend reaching out to our support team. Here’s how:
1. Visit this site: https://help.quickbooks.intuit.com/en_CA/contact.
2. Choose your QuickBooks version.
3. Select a topic.
4. Scroll down and click Get Phone Number.
For now, you can enter the bank transactions manually into QuickBooks.
Thanks for dropping by. Visit us again if there’s anything else you need.
None of these steps fix the issue. This is a product specific error within QB. As you can see by my above post I've been in contact with the support team over the last few months and nothing has been done to fix the issue so far. It's a known issue that is being looked at and is acknowledged... not the same as your fix from the support section. I appreciate the attempt to help, however, posting something like this can cost people a lot of time and frustration as it isn't to do with the issue at hand.
This has already been reported. While our engineers are still gathering data for their investigation, you'll want to enter the missing transactions manually.
We'll update this thread as soon as they've fixed the error.
We're always here to help if you have any further questions.
Can someone please send a work around for importing a CSV file for the bank instead. I am not going to be able to wait for a fix. NEEDS TO BE FOR DESKTOP 2017. The import wizard isn't allowing me to import - this might be because I am set up for bank feeds. I have to say getting clear answers is not easy.
Hello there, MCGC2003 and Trevvy.
In QuickBooks Desktop, you can only use the Excel/CSV file when importing lists. For bank transactions, the software only accepts the WebConnect (.QBO) file.
Here's how to import the file:
Go to the Bank Feeds Center to check the imported transactions.
Though, you can use third-party apps that will help you convert CSV file to a .QBO file.
Let us know if you have other concerns. We're right here to help you.
I've found a partial fix to this issue.
- I downloaded the QBO files for each month I was missing by setting the date range at RBC.
- Once they were downloaded I opened the QBO file with notepad (right click -> Open with -> Choose another app -> Notepad....Make sure the Always use this app checkbox is UNCHECKED)
- Once the file is open in note pad hit Ctrl+F. Search for NAME
- I then shortened each <NAME> entry to 25 characters or less
The Entry was: <NAME> Contactless Interact Purchase - 4589 (36 characters long)
The Entry is now: <NAME> Interact Purchase - 4589 (24 Characters long)
- I repeated the process for each <NAME> entry in each file I downloaded
- When trying to import the webconnect file through File -> Import -> Webconnect file I got an error that there were "No new transactions available" for the chequing account
- I had to create a new chequing account which I called RBC Chequing as Chequing was the name of my original account.
- Renamed RBC Chequing to Chequing and it prompted me to merge the accounts, clicked "yes" I wanted to merge the accounts
- Then imported each file from the oldest to the newest which all imported okay.
The only thing that isn't working properly is the payee. The times, dates, amounts, debits/credits etc seem to all be fine however the payee is being shown as Interact Purchase etc. and there's no listing of the company associated with the transaction. I could be totally of base with this as it's been so long since the software worked that I can't completely remember how it used to import the transactions before the errors started. I don't have any reference point to this as I had to start a new company file from a botched move over to QB Online that didn't go well when I tried to revert to Desktop.
Hope this helps! If anything needs clarification please don't hesitate to reach out.
Hello again, Trevvy.
Thanks for sharing to us the resolution steps you’ve taken to fix the issue. The information provided can help customers who are also experiencing the OL-222 error.
Allow me to chime and clarify why the changes made to the payee didn’t come over after updating the name.
You can only enter up to 32 characters in the payee name field. Once you exceed, the remaining information will appear in the Memo field.
QuickBooks is unable to auto-match payee information, so you’ll have to manually match the transactions. To give you more insights about this, check out the Message: "No new transactions" when importing web connect file article and go directly to Solution 5.
The information I provided should help update the payee name to the correct one.
Stay in touch if you need some help working in QuickBooks. I’ll be right here to assist further. Have a good one.
You mention that after the 32 character limit the remainder is pushed to the Memo entry. I have several entries that are no where near 32 Characters and there is information in the memo field. Does this make sense?
Although a fixed resolution date is unclear at this time, I can assure you that our team is working diligently alongside RBC to get the connection back in tip-top shape. Like my colleagues explained above, you can import your transactions manually in the meantime. I realize that's not ideal, and that you're working with a busy schedule.
My team will surely reach out as soon as we have any updates to share on the situation.
Let me know if you've got questions.
Addie & QB, although I understand it takes time this is totally unacceptable. I need a timeline to have this fixed. What is the timeline? Please elevate. I will also be phoning daily until this is fixed.
Hello again, MCGC2003.
Allow me to chime in and route you to the right direction about the online banking error.
As mentioned by my colleagues, this has already been reported as an ongoing issue. Our engineers are all hands on deck working towards finding a permanent fix.
To save business time, I encourage you to contact our Technical Support Team. Our specialists will need to gather personal details to add your company to receive email updates.
We’re unable to provide a specific time frame yet but rest assured, we’ll keep you posted here in the Community once the resolution is available.
I appreciate your patience while we look into this. If you have additional questions about QuickBooks, please leave a comment below. I’ll be right here to help.
This issue has been ongoing for way too long, we need a fix NOW! We pay a lot of money for your software and entering all our transactions manually is not something I have time to do.
I want to assure you that we're continuing to work side-by-side with RBC to resolve this matter. We know how bank feeds can help save time and make it easy to bring transactions into your QuickBooks Desktop company file, so our goal it to resolve this as quickly as possible. For timelines and updates, please feel free to reach out to RBC support for further information.
I'll be here if you have more questions.
This is getting beyond tiresome. Been using QB for a very long time. 6 months without a fix tells me you folks are not giving this issue the time that is necessary. Very disappointed in what I thought was a company with adequate support for their customers.
There is something going on that we are not being told. My hunch is there is a dispute over licensing fees for use of web connect (.QBO) There is a list of "Approved Banks" that will work with Web connect. We have our mortgage with a coop and they are not approved but did walk us through how to export then import OFX which is Quicken format for non-business. It appears RBC are not the only bank and TD in the US have at least come out and said they were not going to work with Intuit QB
I'm too busy for this nonsense but will try and post if I can get the chequing data in using OFX work around. Always backup first.
I think things here need to be working a lot more Simply. Alternatively we will try a company file import with a competitor. We can't be the victims in clashes of bigger business over money and fees. There's enough of that and we always have a choice in who we trust.
I really wish that we could just get a straight answer. It works for the mastercard account but not the chequing account. How different are they really? Do they have different licensing agreements?
The post above about reducing NAME worked for me even though none of my names exceeded 32. One was exactly 32 characters.
Thanks a bunch for that
I m thoroughly disgusted with QB and RBC for not fixing this yet