Forced migration from Direct Connect to either Express Web Connect or Web Connect

You have it right - so if you want your normal one step update of all accounts to include those, set up express web connect.

One caveat - if your bank provided and you used automatic payment processing/check writing it won't be supported any more via Quicken. It only works on direct connect.

It should not be a one time decision. I use Web Connect over of the unreliable Express Web Connect connection method. If you haven't already, I suggest you review:

Quicken has three methods of downloading transaction data:

Direct Connect: Scheduled downloads. Uses a proprietary Quicken format.and autoposts to Quicken. Direct Web Connect: Scheduled downloads. Screen scrapes data from your bank's web interface and auto posts to Quicken. Web Connect: Manually download a CSV like file, requires that you initiate the import.

Direct Web Connect is better than Web Connect, but only just. Both are slower and more error prone, but cost your bank less.

"Arthur Conan Doyle" wrote

Quicken has three methods of downloading transaction data:

Direct Connect: Scheduled downloads. Uses a proprietary Quicken format.and autoposts to Quicken. Direct Web Connect: Scheduled downloads. Screen scrapes data from your bank's web interface and auto posts to Quicken. Web Connect: Manually download a CSV like file, requires that you initiate the import.

Direct Web Connect is better than Web Connect, but only just. Both are slower and more error prone, but cost your bank less.

------------------------------------------------------------------------------------------

Web Connect does NOT download a .CSV file - it downloads a QFX file. And Web Connect does not "require" that the user initiate an "import" of the downloaded QFX file.

The real name of the Connection Method you identify as "Direct Web Connect" is "Express Web Connect" (at least for Quicken for Windows).

When Express Web Connect works as intended, it is nearly as good as Direct Connect.

The main (and usually the only) problem with Express Web Connect is that it too frequently does not work as intended - and that is almost always attributable to the financial institution. Express Web Connect reliability usually requires that the financial institution web site format remain constant.

Express Web Connect costs the financial institution nothing ... which is why many financial institutions choose it.

[And the most reliable Express Web Connect downloads, actually use what could be called "back door Web Connect", where a financial institution (which most likely already offers Web Connect downloads) provides Quicken (actually Intuit) a "back door" to initiate a Web Connect download when Quicken is doing a One Step Update. "Web Connect" downloads are just as reliable as "Direct Connect" downloads; their only normal drawback is that the user must manually logon to the financial institution web site, locate the individual account(s), and initiate the download from each account. All that extra work on the part of the user is eliminated when the back door Web Connect approach is available for Express Web Connect.

I know of no way to determine whether back door Web Connect is available for an Express Web Connect download.]

Thanks to Marc, Sherlock, Arthur, and John who replied.

Despite getting documentation from the CU that indicated I'd have some decision, Q automatically chose "Express Web Connect", so that's what I am using now. I did get the last 3 months of transactions that I had to review manually to ensure that they had not already been cleared.

(And one less password to remember since the the pw used to set up the account is the same as what I use for their internet banking whereas Direct Connect required a different password used only for that purpose.)

Subsequent downloads have not duplicated any of the previous transactions, and I've received a couple of new ones since the initial large download, so I believe I've off and running.

For future reference about how to remove duplicate transactions read this.

That's very interesting! I have noted this in my 'cheat sheet' I maintain and it might be useful the next time I need to do something like this (which doesn't occur all that often anyway).

Thanks for the pointer.

Turns out I used this procedure a lot earlier than I thought....like the next day. I had to de- and re-activate my Venmo account. This worked like a charm on the dozen or so downloaded (duplicate) transactions. Thanks!