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; } } }

Quicken and Vancity

Boomerang

The ongoing issues relating to customers accessing Quicken through Vancity Savings Credit Union. This is the message I have from Vancity. It appears they are waiting for Quicken to fix this issue.

Hello Bob,

Thanks for the email and the update. I’m sorry to hear that Quicken has not updated their interface so that it syncs with our new app. I reached out to our Online Banking Support Team again to investigate and was told that we have recently reached out to our 3rd‑party aggregators about the need to update their code, and it is taking longer than expected for this to happen. I can appreciate your frustration, and I want to assure you that our team has followed up with them and completed everything that can be done on our end. We have escalated this up.

The timeline I had given you in my last email was an approximation only and based on historical updates. Unfortunately, because the remaining work sits with the third party, we have no means of expediting other than periodically reaching out to them, which our team is doing.

I know this disruption has been inconvenient, and I genuinely appreciate your patience while this is being resolved.

Please feel free to reach out anytime if you have further questions or if there’s anything else I can look into for you.

Take care,

Find more posts tagged with

Online Banking

Windows

QWIN - Canada

Quicken Canada

Comments

Quicken Anja

Hello @Boomerang,

Thank you for sharing that update from Vancity—we appreciate you taking the time to pass that along.

At this time, we do have this active Community Alert regarding Vancity Credit Union connectivity issues, which you can review and bookmark for updates.

This issue has been escalated and is actively being worked on in coordination with our service partners. Unfortunately, we do not currently have an ETA for resolution. As noted in the alert, updates will be posted there as soon as more information becomes available.

We understand how frustrating this disruption has been and appreciate your patience while the issue is being addressed.

Thank you!

LeahMac

Having the same issue. Quicken Classic Version 8.4.2 (Build 804.59835.100).

I'll add that if I export .qfx files from Vancity, Quicken gives an error on import, so it does rather seem like this is a Quicken problem, and not just a VanCity interface issue?

donnainriverwood

Just went though this with Tangerine - I think it took about 3 months to resolve 😒so bad I was looking for a different financial program. Hopefully this one gets resolved quicker.

Boomerang

[Removed - Speculation/Rant]

tmuirhead

I believe this is an issue from the Vancity side, but it may be some incorrect information that Quicken has supplied. I found a workaround that seems to work for using the manual download and import method rather than a direct connection, but you have to delete/deactivate every Vancity update link you have in your file.

I have included more information than probably long-term users need, but new users may not be as familiar with these deeper settings:

from the Vancity website, download the transactions you want to update in Quicken
- select a timeframe that covers back to when your link broke or the last time your reconciled your account(s)
- Download Format is "Quicken.qfx"
in Windows File Explorer (or from the download icon in Chrome), go to the downloaded file location
find the file (it should look something like "Account_Statement_0260_10-Mar-2026.qfx") and right click on the file
select "Edit in Notepad"
there is a whole bunch of information in this file, but you are looking for the "<ACCTTYPE>" entry
- old Vancity banking platform had the account types of "SAVINGS" and "CHECKING" but new platform has "SA" and CA"
- this is where the issue seems to be
- replace "SA" or "CA" with "SAVINGS" or "CHECKING" as appropriate
- save the file
ensure that your online services are deactivated for EVERY Vancity account you may have in your file
- right click on each Vancity account
- choose "Edit/Delete Account"
- select the "Online Services" tab
- select "Deactivate" and confirm this choice
- repeat for EVERY Vancity account that you download transactions to (or had a direct connection to)
- validate that you have cleared everything
  - select "Tools" from the main menu bar
  - select "Online Centre"
  - ensure that neither "Vancity" nor "British Columbia Credit Unions" are shown in the Financial Institutions drop-down menu (if they are still there then you've missed the account shown; if you have accounts at other BC credit unions you MAY have to break their links as well
you should be able to either import the file (File / File Import / Web Connect (.QFX) File) or double-click on the file in File Explorer
- you will be asked whether you wish to create a new account in Quicken or link to an existing (choose this option)
- files should import
repeat as necessary to get things working for the rest of your accounts
you may have to manually delete some duplicate transactions in the update register (highlight the ones you need to delete and then hit the <Delete> button in the reconciliation window

I tested this on my active Quicken file plus a couple of other files to ensure it worked, but I am just one guy hacking away because this broken feature got me a bit peeved. Vancity updated their business accounts to the new platform last night and I did before and after downloads to see where the changes were. The account information changed between the two but that information didn't crash the downloads - only the <ACCTTYPE> field crashed it. I then had to figure out how to get my working file back to accepting them (didn't at first).

I'm going to post this on a number of the other threads on this same topic and will send it to Vancity to clean things up. Hopefully Vancity will update their download protocols so things get back to working and that they will post when things are fixed. If they reply directly to me that things are fixed I will post on this thread.

This thread may be relevant for any other BC Credit Union or ATB customer with a similar issue.

tmuirhead

Further to my previous comments.

I experimented a bit with a new Quicken file and tried the Express Web Connect setup for Vancity and it worked for each of my member cards / account buckets, but still did not work when I tried with my primary member card. Experimented with a member card that just had one account and got it to work by ensuring every account was deactivated and that the "Account Number" and "Bank Card ID" boxes for each account were blank.

<Right Click> on your mouse over each linked account name to "Edit/Delete account" and then select the "Online Services" tab. <Deactivate> or other equivalent button. Then go back to the "General" tab to clear the "Account Number" and "Bank Card ID" boxes (and "Financial Institution" if it is still filled in).

When these steps are done for each of your linked accounts, open the Tools / Online Centre menu from the main menu bar. Vancity Credit Union CA should NOT appear as an available financial institution in the drop-down menu. If it does, you still have another account(s) connected (look at the Transactions below to see what may be still connected).

Doing these steps seemed to reset each of my Vancity accounts to be able to download using the Web Connect process in my relevant Quicken files. Try this first before doing the manual adjustment noted in my previous post. I believe the issue was the change in account type (<ACCTTYPE>) between the two versions of the Vancity banking platform messing things up.

Poco Dan

This is not a Quicken problem, it's a Vancity problem. They are not writing the QFX code properly. I've also got the message from Vancity that it's a Quicken problem. Vancity isn't rushing to fix this.

Quicken Anja

Hello All,

Thank you all for continuing to share updates, findings, and workarounds—there’s been a lot of helpful information contributed here.

At this time, this issue is still part of an active, ongoing connectivity problem with Vancity that has been escalated and is being worked on in coordination with our service providers and the financial institution. Situations like this involve multiple parties (the bank, aggregation services, and Quicken), which is why resolution can sometimes take longer than expected.

We understand there has been some confusion around where the issue originates. While we can’t speak in detail to the bank’s internal systems or timelines, what we can confirm is that this is not yet fully resolved on the backend, which is why users may continue to experience connection issues or errors.

For now, we recommend continuing to follow the Community Alert for this issue, as that is where any official updates or resolution details will be posted as soon as they become available.

We recognize how disruptive this has been and truly appreciate everyone’s patience while this is being worked through.

Thank you!

Boomerang

I still am having the same issue since January 21, 2026.

I always get an error message : Quicken is unable to complete your request (OL-221-A)

This error message is different than what others have received.

Any suggestions?

Scouter_Don

I have been having the same issue since January 2026

I always get an error message : Quicken is unable to complete your request (OL-221-A)

I have complained to Vancity several times but Vancity blames it on Quicken. To be precise, Vancity each time advised me that they do not guarantee that downloads to 3rd party programs (i.e. Quicken etc) will work and the person I spoke to refused to pass my complaint onto Vancity's IT Department. But reading the post from tmuirhead on March 10, 2026 it seems that it is Vancity that has caused the problem.

I wonder if the moderator QUICKEN ANJA could reach out to Vancity about this and point out the issues described in the post from tmuirhead on March 10, 2026.

In the meantime I have stopped using Vancity as one of my bankers, and told them why. They were upset saying it was unfair for me to take my business elsewhere when it was not their fault.

Quicken Anja

Hello @Boomerang & @Scouter_Don,

Thank you both for sharing additional details about what you’re experiencing.

The OL-221 error typically indicates an issue with the connection or with the data being provided by the financial institution. Even if you’re able to sign in successfully on the bank’s website, Quicken may still return this error if the data or file being sent isn’t in the expected format.

A few key things to keep in mind:

If you are using Web Connect (QFX file downloads) and receive this error, it usually points to an issue with the file itself, which would need to be resolved by the financial institution.
If the account is set up with Direct Connect, the financial institution would need to investigate further, as Quicken does not have access to their servers to correct those types of issues.
In some cases, this error can also be caused by temporary server issues or changes on the bank’s side, so trying again after some time may help if it’s intermittent.

Regarding reaching out to Vancity directly—our role as moderators here in the Community is to provide guidance, troubleshooting steps, and escalate internally when appropriate. For bank-specific data or connection issues like this, resolution needs to come from the financial institution’s side. You will need to contact Vancity and request that they investigate the issue on their end. We recommend asking to speak with a supervisor or Tier 2 specialist, as they are typically more familiar with third-party integrations like Quicken.

Thank you!

Arctic Hare

https://community.quicken.com/discussion/comment/20547384#Comment_20547384

There is zero, zilch, natta, nothing, none whatsoever support for Direct Connect in Canada. It's not Direct Connect.

Tony1000

Hey all, just wanted to chime in, another Vancity/Quicken user here, I have exchanged messages with both Vancity and Quicken on the issue of QFX downloads from the new Vancity online banking, and it is very definitely a Vancity issue.

To be clear, Quicken has told me their software for importing QFX files is compliant to the OFX standard for financial data interchange. As others have noted there are several things Vancity changed in the QFX downloads that broke this.

According to the OFX standard, in the BANKACCTFROM object, the correct value for ACCTTYPE should be CHECKING for a chequing account and SAVINGS for a savings account. Vancity changed it to CA for a Vancity chequing account and SA for Savings Account. A temporary fix is to edit the QFX file in a text editor and change it to the correct value for that account.

Also according to the OFX standard, the maximum length of the NAME and MEMO tags in STMTTRN objects is 32 characters or less. Quicken said they are compliant to this, but the software seems to accept up to 64 characters. Anything more than 64 characters will cause a Parse Error.

In the new Vancity system, some transactions now exceed this limit, for example, a funds transfer between accounts looks like this:

Funds transfer-online from Jumpstart High Interest 101000nnnnnnnn

This tag is 65 characters long. A quick text edit determined that shortening it by one character to 64 characters resulted in no Parse error on import.

Manually changing the ACCTTYPE and shortening NAME and MEMO tags in the QFX in a text editor has so far worked for me.

Quicken Anja

Hello @Tony1000,

Thank you for taking the time to share these detailed findings—this is very helpful.

Based on what you’ve outlined, it does appear that recent changes to the QFX file formatting may be contributing to the import errors users are experiencing. We appreciate you also providing the workaround steps that have been working on your end.

At this time, since this involves how the data is being formatted in the downloaded file, the issue would need to be addressed by the financial institution to ensure compatibility.

We’ll continue to monitor this thread, and we appreciate everyone sharing their findings and workarounds in the meantime.

Thank you!

Tony1000

Hey! Some good news! Just downloaded QFX files today (Apr 28) from Vancity, and the ACCTTYPE tag bug has been fixed. The tag is now coming through correctly as "CHECKING" or "SAVINGS". One note, Vancity was incorrectly using "CHECKING" for both chequing and savings accounts. They have corrected that too. This means the first time you download and import a QFX file for a savings account, Quicken will prompt whether to create a new account or link to an existing one in your Quicken data - be sure to select "Link to an existing account" and choose your exising Vancity savings account in your Quicken data.

Meanwhile, they have not fixed the problem with excessive characters in the NAME and MEMO tags. Some of these are still exceeding what Quicken will ingest and causing a Parse Error. You still have to manually edit these fields in a text editor or get clever and write some scripts to do it before importing the file.

Quicken Anja

@Tony1000 Thank you for sharing this update—it's great to hear that the ACCTTYPE issue has been corrected on Vancity’s end, and we appreciate you calling out the important note about linking accounts during import.

Regarding the remaining issue with the NAME and MEMO fields exceeding character limits; since this relates to how the QFX file is being formatted, it would also need to be addressed by Vancity to ensure full compatibility—hopefully they will being doing that soon too.

In the meantime, we appreciate you continuing to share your findings and workaround—it’s very helpful for others experiencing the same issue.

Thank you!

Boomerang

Hello: An update. I have been for several weeks downloading from Vancity Savings and Credit Union and manually editing the file, namely to CHECKING and then establishing a successful update. April 28, 2026 I had a successful download direct into Quicken with no issues.

Sadly in the evening, this was not the case. The download failed with the same error message I have had since January 2026. The ACCTTYPE is correct so there is nothing to edit. I have now sent the QFX downloaded file to Vancity and for there IT Department to investigate. I am curious, did Vancity change more than just the ACCTTYPE? I am waiting for their response.

It would be good if others still have issues, post them here to establish an overview of what is happening.

Thanks.