nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Vancity OL-220-A Issue remains unresolved for my chequing account

gfcoll43

Vancity Credit Union changed its Online banking platform 5 months ago. Subsequently, none of the accounts would download to Quicken, and would show error OL-220-A. After a few months, a change in coding (ACCTTYPE)was fixed. Now I am able to Download Transactions in only SAVINGS type accounts. Downloading transactions for the CHECKING type accounts still results in error OL-220-A.

Previous posts regarding this error gave some temporary solutions involving editing code in the download file, however these do not work for me.

Is there a solution for this?

Find more posts tagged with

Comments

Quicken Laura

Hi @gfcoll43,

Thank you for sharing the details of the issue you're experiencing. I'm sorry to hear that you're still encountering the OL-220-A error with your checking accounts.

To help us better understand the situation, could you please confirm whether your Vancity checking and savings accounts are set up using the same connection method (for example, Web Connect, Express Web Connect, or Direct Connect)?

To check the connection type:

Open the affected account.
Click the Gear icon in the upper-right corner of the register.
Select Edit Account Details.
Click the Online Services tab.
Review the connection method listed there.

Please let me know which connection method is shown for each account, and whether both accounts use the same one.

I look forward to your response.

gfcoll43

Thank you for your response. All the accounts that are set up to download and import transactions have Connection Method of Web Connect. Some of the Savings accounts and Registered Plan accounts exhibit Error OL 220 or 221 as well as the Chequing account. It is interesting that some work, and some don't, but they all have Web Connect Connection Type

Quicken Laura

Hi @gfcoll43,

Thank you for your response.

Based on the error message you described, this issue may be related to the QFX file itself. As noted in our support article:

Web Connect (Importing a QFX file from your bank's website) - Receiving this error when downloading a QFX file directly from your bank's website indicates an issue with the file itself. You will need to contact your bank to resolve this issue.

If you have not already done so, I recommend disconnecting the affected account(s) and then attempting the import again. When importing, be sure to link the downloaded transactions to the appropriate existing account. This can help determine whether the issue is related to the account connection.

Steps to import QFX

Back up your Quicken Data File.
Go to the File menu and select File Import → Web Connect (.QFX) File. The Import .QFX File screen will appear.
Use the Browse button to find and select the file you want to import.
Click Open or double-click the file to import.
When prompted, choose Link to an existing account and select the correct account from the dropdown menu. (Alternatively, choose Add a new account if you are importing data for a new credit card or bank account).

If the issue persists after trying these steps, I recommend contacting your bank directly so they can review the file and verify that there are no issues on their end.

Please let us know how it goes or if you have any additional questions. We are happy to help.

gfcoll43

Thank you. I will try to connect with Vancity Credit Union to review my issue. I have tried the steps suggested without much success with the Chequing account as well as the Savings accounts that are affected. I have not had any success with Vancity in the past. Perhaps this time there'll be success.

gfcoll43

I decided to try the steps you outlined (Steps to import QFX). However when selecting Quicken File Format QFX, no files appear. So I selected Web Connect QFX format, the files appeared.. selecting the appropriate file to import resulted in same OL220 error

Quicken Laura

Thank you for pointing that out. I've updated the instructions to reflect the correct steps.

If you have an opportunity to speak with your bank, I would appreciate it if you could share any information they provide here. Their feedback may help us better understand the issue and determine the appropriate next steps.

I look forward to your update.

gfcoll43

Will do. Thanks Laura

Tony1000

Hey all, Vancity have still not fixed the problem with the NAME and MEMO tags being too long. It is definitely their problem, they have seriously munged these two tags ever since the on-line banking upgrade early this year. Before the upgrades, it was fine, the NAME contained the name of the merchant or institution for a transaction, and the MEMO contained additional info like the type of transaction, e.g. Point of Sale, e-Transfer, etc. Since the upgrade they have simply strung all that text together so it sometimes, depending on the length of the name and type of transaction, exceeds what Quicken will ingest. Any NAME or MEMO tags that are greater than 64 characters will cause a Parse Error, or throw a OL-220-A/B error on importing to Quicken. The only solution right now, until Vancity fixes this properly, is to use Web Connect to download a QFX file, edit the offending tags so they are 64 characters or less, then import it into Quicken.

Also see my earlier comments here:

https://community.quicken.com/discussion/comment/20550354#Comment_20550354

gfcoll43

here is Vancity reply Thank you for reaching out to Vancity. I’m really sorry to hear this has been an ongoing issue for you, and I understand how frustrating it must be—especially given how important downloading transactions is for managing your accounts in Quicken.

Since the launch of our new digital banking platform earlier this year, there have been some challenges with third‑party integrations like Quicken. This can affect how accounts authenticate and may result in inconsistent behaviour, such as certain accounts downloading successfully while others—like Chequing or Registered Plan accounts—do not. What you’re experiencing aligns with known issues we’ve been working to address alongside external providers.

At this time, we aren’t able to make changes directly within Quicken or control how their system connects to ours. As a temporary workaround, you may consider downloading your transactions in CSV format from online banking and uploading them into Quicken manually. I appreciate this isn’t an ideal solution, and I’m truly sorry for the inconvenience it causes.

Please know that your feedback has been noted, and I will ensure your concerns are shared with the appropriate teams for continued review. We’re actively working with third‑party providers to improve connectivity, and functionality may improve as those integrations are updated.

If there’s anything further we can assist you with in the meantime, Gerry, please don’t hesitate to reach out.

sad. Seems Tony (see below) has figured it out.

Gerry