Quicken-Wells Fargo issue - all my fault

Well, YOU are STILL a client of Wells Fargo. What does that say about YOU?

Of course, are you married? If so, you know it's all your fault and has been since you said, "I do." So you should be used to it.

You need to ask SS and the maker of the other check to trace them, good luck!

snipped-for-privacy@nada.com wrote in news: snipped-for-privacy@4ax.com:

Over the years I've had a handful of transaction (from varioous banks, not just WF) that were never downloaded into Quicken. I juet cleared them manually.

Wells Fargo gives me free Quicken bill pay because it was grandfathered from Wachovia. Everybody else want's about $10 a month. And changing banks for checking, with all the automatic payments, is a pain in the ass.

And inspite of their insisting that it wasn't their fault, they did eventually show up, more than a day after appearing in the online statement.

I can fully understand your grief about changing banks, when one has already set up multiple automatic payments. However, I CAN NOT understand why anyone would need Quicken bill pay. The pre-authorized payments I have set up at the banks and credit card company take care of 99% of my regularly occurring bills. The odd ball one can be down via Pay Pal or my bank's web site. No need to complicate things with the unneeded, troublesome Quicken bill pay.

"Sharx35" wrote in news:k5ibg7$v3l$ snipped-for-privacy@dont-email.me:

When you have several accounts at multiple financial institutions, it is very convenient to manage everything in one place.

There is a difference between using Quicken Bill Pay and Wells Fargo online payment through Quicken. I suspect the OP has the latter because WF cannot waive Quicken's fees, only its own. I use online payment through Quicken and WF waives fees. That way I can use direct connect instead of web connect.

The OP may have an issue with his online settings and might try deactivating, closing Quicken, deleting the OFX log, and reactivating online services, all after backing up the file first.

Actually it was not an issue with anything on my system. Wells Fargo support lied/was ignorant of what was happeing on their side. It got fixed by waiting a day until WF did whatever they needed to do.