Skip to main content
September 6, 2024
Question

Unable to connect to Citicards since Sept 2nd. (QB Desktop Pro Plus 2024)

  • September 6, 2024
  • 31 replies
  • 0 views

Ever since Sept 3, 2024 I have been unable to connect to Citi cards for any account. My last successfully connection was on Sept 2. Prior to Sept 2, I have downloaded transaction with no problem for.... a long long time almost every business day.  It is a core part of my workflow. All of my other bank feeds (e.g. Wells Fargo, AEX, Morgan Stanley, Chase) are all working correctly with no issues.

 

I spoke with QB support and they continue to treat me like a newbie idiot. I have used QB to download transaction for many years and understand what I am doing.

 

Anyone have any thoughts?

31 replies

netispguyAuthor
September 26, 2024

September 26, 2024:

 

Day 13 since last working.

 

Please escalate to Tier 3.

 

Total days not working in September 2024: 22

 

If anyone is interested, the investigation case is INV-112003

netispguyAuthor
September 27, 2024

September 27, 2024:

 

Day 14 since last working.

 

Please escalate to Tier 3.

 

Total days not working in September 2024: 23

 

If anyone is interested, the investigation case is INV-112003

netispguyAuthor
September 27, 2024

INTERESTING UPDATE

 

Besides Quickbooks, I also use Quicken for my personal finances. Guess who Quicken uses for bank feeds??? Yup, you guessed it... Intuit.

 

Today Quicken stopped downloading all transaction from Citibank. Here is their comments:

 

Our teams have discovered an issue where a majority of Citi Bank users have been experiencing incorrect transactions downloading during One Step Update in Quicken for Windows and Quicken for Mac.

This has been escalated internally, though we do not have an ETA at this time.

 

We will be blocking all Citi financial insitution connections while we work on a resolution. As a result, users may encounter an FDP-390 error when attempting to update or add accounts. There is no current ETA. 

 

Thank you!
(Ticket #11296799)

netispguyAuthor
September 30, 2024

September 30, 2024:

 

Day 17 since last working.

 

Please escalate to Tier 3.

 

Total days not working in September 2024: 26

 

If anyone is interested, the investigation case is INV-112003

October 1, 2024

I'm in the same boat. Since early September. I hope they will actually give this issue some priority.

netispguyAuthor
October 1, 2024

Good News. it works!

 

This morning I got notice that Intuit had fixed Quicken, which I verified worked. So,I launched Quickbooks, which  immeditaly did a major update. 

 

After the update and re-launching, I tried to add Citi cards again and this time it actually connected with no errors! I was able to re-establish the bank feed connections to all of my Citi accounts. I am hoping that this is finally the fix we have been waiting for.

 

-Scott

October 1, 2024

Oh my gosh Scott! You are my hero!! Will do the same and let you know the outcome.

 

THANK YOU FOR YOUR PERSISTENCE!!!

October 1, 2024

i agree.

 

thanks for pushing them to finally fix it

October 2, 2024

A little off topic but looks like this update may have caused other issues! Anyone else notice after doing the update that in reporting, when you change the date or any filters that the font shrinks on screen and printing?

October 2, 2024

Yes-same font problem that you have.  Very disturbing

October 5, 2024

FIXED: I've been unable to download Citi transactions since early sept.  Did all the recommendations - finally a QB update release "today" 10-5-24, fixed it.  Now I can download direct again.  NOTE: you ALSO have to login to your Citi account and allow the connection.  I also had to remove the OLD QB connection as it was listed as QB 2021 (I have 2024) by Citi.  https://online.citi.com/US/ag/ofxConsentPage 

netispguyAuthor
October 17, 2024

Guess what??? It seems like Citi feeds are broken once again. 

 

Anyone else having problems again?

 

-Scott

October 17, 2024

I just downloaded through bank feeds about an hour ago with citi... so unless I timed it right... I'm still good. That connection does through me off though, as there's the pop up password required as opposed to the Amex connections. Could it be hiding behind another window? or are you going straight to the same error as before?

netispguyAuthor
October 17, 2024

Yes... Same error as before for both doing a Bank Feeds download and trying to add a new Citi Card account...

 

I have checked for updates and rebooted a few time... same thing.. Ugggg

 

-Scott

October 17, 2024

Just now (10/17/2024) Citi Card connect started working again. The steps I took

 

Run Rebuild - reported no errors

 

Closed Company File - File > Open or Restore Company > Selected my existing company file

 

Went to bank feeds, selected one of my two Citi card accounts, entered my password, and it actually worked, downloading all the old transactions dating back to early Sept 2024.

netispguyAuthor
November 13, 2024

If anyone is still having issues with their citi feed, please let me know. I believe I have found a fix (and it's one QB support won't tell you about.)

 

-Scott

November 13, 2024

Would love to know for next time - I assume you are fixed now?

netispguyAuthor
November 14, 2024

Yes I am fixed. FYI, we are an IT, Datacenter, Sysadmin and Network consulting group, so going into the Windows or Mac file systems to seek out config files and caches are not new to us.

 

I had to go into the Quickbooks software configuration files for OLB and make an adjustment. I am not going to share specifics right now as I am sure this is not an approved Intuit fix, but it had an immediate effect that seemed to fix things. Even after completely uninstalling Quickbooks, we noticed some remnants did not get removed and the problem was still there after a fresh installation.  One of the persistent files had a reference to Citi and was in txt format, so easy to edit. We saved the then current version, edited the files and modified the reference to Citi, restarted Windows and launched Quickbooks. The Citi feed worked as expected the first time. 

 

I would like to report this "fix" to the Quickbooks team, but during this entire issue I do not speak with a singe person who I believe would understand what we did/found. 

 

-Scott