Citi card downloads not working, method of download changed?

Since you previously had DC via the Citi Cards connection setup, you might want to consider doing the following. Be sure to follow the steps to the letter or you will probably have EWC+ connections, again.:

1. If you have not already done so, you might want to enter and save the Opening Balance transaction dollar amount into the Memo field. Do this for every account (not just the Citi accounts). It is not mandatory to do this but it can save you a lot of time troubleshooting account balance issues that might pop up when changing account connection methods because sometimes doing that will change the dollar amount of those transactions. Having the correct dollar amount saved in the Memo field can made it very easy to know when this issue has occurred and what you need to do to correct it.
2. Back up your data file.
3. Go to the Online Services tab of Account Details and click on Deactivate. Do this for both of your Citi cards.
4. Then go to Add Account and TYPE IN Citi Cards in the search field. DO NOT click on the Citi Cards or Citibank buttons.
   
5. Click on Advanced Options…DO NOT click on Next.
   
6. Click on Continue > select Direct Connect > click on Next > follow the prompts to complete the DC setup. NOTE: If you are taken to your online account in your browser just cancel the action and start Add Account again. This will only happen if you did not precisely follow the steps here.
7. When prompted by Quicken, make sure to LINK the downloaded data to the accounts that are already in Quicken.

When completed, your 2 Citi cards should be set up with DC, again.

@JQuick1 -

I have just accepted I am going to use EWC+, as no one from Quicken has stated that the Citi DC is expected to still be working.

Have you reported this to Quicken Support? That is likely the only place you will hear Quicken every saying that.

It is always always safe to assume that if the Fidir.txt (Financial Institutions Directory) file shows that DC is supported then, unless there is some specific connection issue at the time. The Fidir file contains the list of every FI that supports Quicken, which types of accounts in Quicken that they support and the connection method(s) that they support. Citi Cards and AT&T Universal Card FIs are the only two Citi FIs that I am aware of that still support DC but they are limited in which cards can be used with them.

It also appears that unless one follows the the instructions to setup the DC connection using Advanced Options, then the connection will default to EWC+ or EWC (depending on the specific card).

Further, the "Last Access Time" in your Citi Data Management Hub screenshot above is 9/28 - are you getting an updated date that is more current after a recent download attempt???

Yes, it updates every time. The picture shows an older date because that was the date that I'd taken that screenshot picture. Instead of repeating the screenshot process I simply copied the picture file that I'd created on 9/28. The main purpose of that screen shot is to show what one needs to click on if Quicken access is not shown there.

Also, as I have shown and stated previously, such as on 10/3 above in this thread, the Citi Costco won't even add "Quicken Windows" entry after logged into the Citi Data Management Hub. I click on "Add Access" and a blank page is returned. In addition, the Double Cash Citi card has a "Quicken Windows" entry, but DC doesn't work for this either, and the "Last Access Date" doesn't update(9/27).

Late last night I encountered a problem on the Citi.com website and I could not access the Data Management Hub at all using the link they provided. What I then did was, while logged into my online account, type in "https://citi.com/datamanagement" and then I got a popup asking if I wanted to allow Quicken to access my data on Citi.com. I accepted it and then went to a test account in Quicken to do Add Access with Citi Cards for DC (using the Advanced Options) and DC was set up and functioning.

So, yes, it appears that the Citi.com website is a bit broken with regard to this and Citi needs to fix it.

I believe this is due to recent backend changes and further, I believe people from both Citi and Quicken know what is going on in more detail. Ultimately, this problem has to do with change control and poor communications of these changes, which are requiring the Quicken customers to make manual client changes, as well as dealing with a broken application for far too long. If this was expected, then why no prior notification? Even if not expected, better comms about what is going on and more urgency in fixing needs to be done.

Yes, what you say is very possible but we'll never know all the details behind the cause of the issue. Quicken stated that their service provider (the company that is the aggregator providing the data transference connection between the EWC/EWC+ FI and the Quicken software….Intuit) was working the issue which tells me that there was some major data transfer breakdown that occurred between Citi and Intuit. That is also reinforced by the first Alert that was posted in this forum about Citi downloads including incorrect transactions. I fully do agree that all 3 parties were to some degree involved in the resolution of the issue which also contributed to some of the delays encountered because the more parties that are involved the more complex the more complex the logistics.

Closing discussions as "Resolved" when customers say they are not resolved, requiring opening new threads on the same problem, is unacceptable.

Generally, Quicken Moderators will keep post threads open for 2-4 wks after the last post has been made. Then whether or not anyone has posted that the issue has been resolved the thread will be closed because it will be assumed that the issue has become "stale" and no longer an issue. I support this because old threads that are kept open longer than this generally become clutter and serve no purpose. It's better to open a new thread and, if appropriate, copy/paste the URL from the closed thread as reference.

In this particular Citi debacle, Quicken decided to close the threads as soon as they got confirmation from Intuit (and probably from their own Development & Quality teams) that the issues were resolved. Generally, I would not agree with closing the threads so quickly but in this case I was relieved to see them do that. The threads had become very long and unwieldy…heck, one of them was 27 pages long. When they get too long they really aren't very effective anymore because most people simply do not go back and ready through all the posts. And I was getting 100+ notification emails a day which consumed much of my days just trying to sort through them all. So, yeah, I was really ready for those threads to be closed.

I know for myself that if they had not closed those threads I would no longer have posted anything in them and I would have blocked all notifications for them because it otherwise would have been a complete waste of my time. So, IMHO, closing those threads post-"fix" was perhaps the best thing to do to "clean out" all of the clutter from those no longer pertinent posts about the original issue and workarounds. Instead, let those who were continuing to have connections/download issues start new threads. And it turns out it appears closing those threads was highly effective at cleaning things up because the number of posts by those still having connection and download issues now is pretty small compared to what it was pre-"fix". Now these fewer, smaller threads can get better, more specifically focused attention by others making them more effective threads. So, I'm happy with the results.