In Quicken Web Connect vs Express Web Connect, the difference is who does the fetching. With Web Connect you sign in to your bank's website, download a QFX file and import it. With Express Web Connect, Quicken's aggregation partner updates your accounts each night using stored sign-in details. Your bank's support decides which methods you can use.
How Quicken Web Connect moves transactions by file
Quicken Web Connect moves transactions by file: you download a QFX from your bank's website and Quicken imports it. Quicken's article on how it connects to your bank says that with Web Connect you must download the file manually to update transactions and balances, and that your login information is not stored in Quicken.
In practice, a Web Connect update looks like this:
- Sign in to your bank's website as you normally would.
- Find the download or account history page.
- Choose the Quicken format and the date range.
- Download the QFX file.
- Open it in Quicken, or import it from Quicken's file menu, and assign it to the right account.
Nothing happens until you do it. That is the main cost of Web Connect, and also its main comfort. Your bank password stays between you and the bank. You choose exactly which dates go in and when.
Because each update is a file, Web Connect gives you something to inspect if an import goes wrong. You can open the QFX in a text editor and look at it. When Quicken refuses one, the guide to fixing a Quicken QFX import error in the file or the account works through the usual causes.
How Express Web Connect updates Quicken overnight
Express Web Connect updates Quicken overnight without any file from you. Quicken's connection article says access and retrieval of data is automated through nightly updates, and that your login credentials are stored on Quicken's aggregation partner's servers. When you open Quicken and update, the lines collected for you come in.
On Quicken for Mac, the same method goes by a different name. Quicken's article says the Mac version uses the term Quicken Connect instead of Express Web Connect, and that on a Mac the sign-in details are kept in the Mac Keychain rather than in Quicken.
The appeal is obvious. Nobody has to remember to download anything, and every account at that bank stays current with one update. For a household with several cards and accounts, that saves real time.
The cost sits on the other side. Your bank sign-in details are held by a third party so it can sign in on your behalf. And when the bank changes its website or adds a security step, the nightly collection can stop until the connection is repaired.
Where does Express Web Connect+ keep your bank login?
Express Web Connect+, or EWC+, doesn't keep your bank login at all. Quicken's connection article says you are sent to the bank's website to sign in, and a secure token is then passed to Quicken and stored by the aggregation service. Your bank credentials are never stored, and you can revoke the token at any time.
The token works like a key the bank has issued for this one purpose. The bank knows about it and can cancel it, and so can you. That is a different arrangement from handing over a password that also opens your online banking.
Quicken's article says Quicken for Mac supports EWC+ for the same institutions as Quicken for Windows. So the choice between EWC and EWC+ follows the bank, not your computer.
From day to day, EWC+ behaves like Express Web Connect: updates arrive without files. The differences show up at setup, when you sign in at the bank, and later if the token expires or is revoked, when you sign in at the bank again.
Who decides whether your bank uses Web Connect or Express Web Connect?
Your bank and Quicken decide which method your accounts use, more than you do. Quicken's connection article says the method depends on the services your bank supports, your preferences and Quicken's relationship with the bank. Quicken always starts with Direct Connect where a bank supports it, and otherwise sets you up with Express Web Connect or EWC+.
Direct Connect is the fourth method and worth knowing. Quicken's article describes it as a two-way connection: Quicken sends a request to the bank, which can also cover services such as bill pay and transfers. You may need a separate sign-in from your bank's website, and the bank may ask you to sign up for it.
Your own choice comes in at the edges. If your bank supports Express Web Connect and also offers a Quicken download on its website, you can still download QFX files and use Web Connect instead of turning on the automatic connection. If your bank offers no automatic method, Web Connect may be the only way.
This also affects other programs. The Moneydance guide to download methods notes that if a bank supports only Web Connect or Express Web Connect, Moneydance can't use Direct Connect with it. Banks pick their connection services, and every finance app works within those choices.
Web Connect and Express Web Connect compared row by row
Web Connect and Express Web Connect compared side by side come down to effort against control. Web Connect needs a download each time but stores nothing. Express Web Connect needs nothing from you after setup but keeps your sign-in with a third party. EWC+ keeps the automatic updates and replaces the stored sign-in with a token.
The table draws on Quicken's connection article.
| Web Connect | Express Web Connect | Express Web Connect+ | Direct Connect | |
|---|---|---|---|---|
| How lines arrive | You download a QFX file | Nightly automatic updates | Automatic updates | Quicken requests data from the bank |
| Your bank sign-in | Not stored in Quicken | Stored by the aggregation partner | Never stored, a token instead | Often a separate ID, not stored by the partner |
| Two-way services | No | No | No | Yes, where offered |
| Work for you | Every update | Setup, then little | Setup, then little | Sign-up with the bank |
Read the table by asking what bothers you more. If stored passwords bother you, Web Connect or EWC+ fit. If remembering downloads bothers you, any automatic method fits better. If you need transfers or bill pay inside Quicken, only Direct Connect offers them, and only at banks that support it.
When a manual QFX file beats both Quicken connection methods
A manual QFX file beats both connection methods when you need control over dates. That covers bringing in history from before the connection started, filling a gap after a connection broke, setting up an account at a bank with no Quicken support, and closing out an account that no longer exists.
Here are the cases one by one:
- Old history. Months from before you set up the connection may never arrive through it. A downloaded QFX can cover them. A QFX built from statements may work too, though Quicken says it does not support files made by conversion software.
- A broken connection. If Express Web Connect stopped for two weeks, a QFX covering exactly those days fills the hole.
- No support at all. Some small banks and credit unions offer no Quicken connection. A file is then the only route.
- A closed account. Once an account is closed, the connection ends, but you may still need its last months.
Sometimes the file you have isn't a QFX. A bank may give you a plain OFX instead, and whether Quicken will take it is its own question, answered in the post on whether Quicken will import an OFX file. If all you have is a spreadsheet of transactions, the guide to an Excel to OFX converter and what it needs from your sheet explains how a sheet becomes a bank file.
If your books are in QuickBooks or Xero rather than Quicken, a different file is the target. SimpleBankConvert is being built for that case, turning PDF statements into CSV or QBO files, and you can sign up to hear when it opens.
Mixing Web Connect files into an Express Web Connect account
Mixing Web Connect files into an account that already updates by Express Web Connect is the most common way to get duplicate transactions in Quicken. The automatic connection and the file can both deliver the same purchase. If the two copies don't carry the same transaction ID, nothing tells Quicken they are one payment.
The transaction ID is the key. The OFX 2.2 specification says each FITID identifies one transaction within an account and exists so software can detect duplicate responses. A bank's own QFX download carries its IDs. Lines collected another way may not match them, and a file built from a PDF statement carries IDs made by the converter.
To fill a gap without doubling lines:
- Find the last date the connection delivered before it stopped, and the first date after it resumed.
- Download or build a QFX covering only the days in between.
- Import it into the same account.
- Review the new lines and accept only the ones that are not already there.
- Compare Quicken's balance with the bank's balance for the last day in the file.
If duplicates got in, remove the extra copies before you categorize or reconcile. Categorizing both copies doubles the spending in every report, and the mistake gets harder to see each month it stays.