Digital Federal Credit Union Issues (QMAC)

[EDIT: Separate threads about this problem have now been merged.]

ishiver said:

Would be great to know what caused the disruption and whether it is with DCU's new system or with Quicken changes. I've personally grown tired and frustrated over the integration between Quicken and this financial institution. I just want the product to work when I log in....plain and simple.

We almost never hear why there was a problem, or what it took to fix it. In many cases, the folks at Quicken may not even know, since the connectivity issues are contracted out to Intuit.

In general, most connectivity problems are not caused by an update to Quicken, but by a change at a financial institution. If a financial institution makes changes, large or small, it can often break Quicken's (Intuit's) connectivity. Financial institutions can try to make things go smoothly by communicating with Intuit in advance of upcoming changes, documenting what will change, and even providing a staging server environment for testing. But most of the time, that doesn't happen. Consider that for any financial institution, the percentage of their customers who use Quicken is probably quite small, so the financial institution's IT staff probably has Quicken connectivity near the bottom of their priority list — if they even remember it.

In this case, it sounds like the credit union changed their back-end systems, so there's almost no doubt that's what broke the connectivity with Quicken. When that happens, Intuit first needs to be notified that things aren't working, and then they need to investigate the cause; in some cases, they can program a fix themselves, while in other cases, they need to communicate with the financial institution or work with the financial institution on changes at both ends. We, as end-users, never get any details about any of that process. One day, things just suddenly start working again.