Ahhhhnnnnd Now the font size is all screwed up when I go back to a report after opening a transaction. If it's not one thing it's another... 

This worked!!!!  I had it set to automatic updates, and it said everything was up to date, but I updated again anyway.  Also, Before I added the Bank Feed for Citi back, I went to CitiCards Profile>More Settings>Security>Manage Desktop Apps>Add Access button.  I had previously deleted my Citi access while troubleshooting.  May be worth checking if the updates do not work.  Thank you for this summary, fdr!

Thank you for sharing your insights, HBLL, and for raising your concern, CWalters. I have some details that will help ensure the report’s fonts appear as you need them.

We can utilize the Customize Report option to adjust the font size, enhancing clarity and presentation in your reports.

1. Go to the Reports menu, then choose a specific report.
2. Click on Customize Report, then select Fonts & Numbers.
3. Tap the Change Font button, then adjust the font size from there.
4. Hit OK.

You can also modify the fonts from the Edit menu. Here’s how:

1. Go to the Edit menu and select Preferences.
2. Click Reports & Graphs, then select the Company Preferences tab.
3. Tap the Format button.
4. Select Fonts & Numbers.
5. Change the fonts as desired for each category.
6. Hit OK.

If the issue persists, check this link for another solution: Fix screen issues in QuickBooks Desktop.

Finally, in case you want to personalize your reports, check out this article for more guidance: Customize reports in QuickBooks Desktop.

You can tag my name if you have additional questions about the font size of your reports. I'll be more than happy to assist you further.

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 

Had a chance to update QB today and then I was able to set up the bank feed for Citibank which was tortuous as finding that screen to authorize the link was not trivial so I am posting it here to help future users avoid tearing out their hair as I did today. You're welcome!

Once you are logged into Citibank go to:  https://online.citi.com/US/ag/ofxConsentPage

Once I clicked on the Add to allow me to login, it all moved forward smoothly as in the past. I honestly can't believe the way this thread was handled and this should be used as an example for customer service management as to how not to handle a serious problem. 

There is a pop-up in QB when setting up the Citibank online banking portion that says to go to https://citi.com/datamanagement to setup third party access - I just could not recall the exact link at the time I posted that last entry.  Citi then gives you 10 minutes to complete the QB setup before you are required to make an additional request for access at https://citi.com/datamanagement

Thank you for the link.  I agree that this was how NOT to handle an issue.

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

Anyone else having problems again?

-Scott

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?

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

I'm still good, just checked - but I'm also running Enterprise 24.0 and there was just a major update this or last week I think. At least on my version it's still ok. Sorry, you're dealing with it again!

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.

Hi all,

There were TWO patches to Desktop (2024 for me) released recently - force a QB update even if you did it recently.

I'm on R9_55 and my Citi downloads are working today.  They were also working on R9_50 (the first recent patch) https://quickbooks.intuit.com/learn-support/en-us/help-article/update-products/release-notes-quickbo...

I just did the re-install of all patches... I am on R9_55..

Still broken.  I disabled the Citi bank feed, and tried to re-enable. Just like last time, I am now getting  the OLSU-1011.

This sucks again,

-Scott

Scott,

Did you previously log into your Citibank online account and "authorize" downloads?

I suggest doing that regardless of it working or not as it needs to be done to refresh something on the Citi side.

...complete the QB setup before you are required to make an additional request for access at https://citi.com/datamanagement

@JW42 Yes Already did that; however, if I cannot even get to a screen that allows me to enter my user name and password, it won't even get to the step that checks for access.. understand?

I just checked and mine are still working at this point.  Fingers crossed.  I received an email about another update but I haven't done it yet.  The subject line is: Update now to QuickBooks Desktop Plus ‌2024 R9 for the latest functionality

My connection stopped working on Friday, 10/18. I've attached the QB message I'm receiving. Has anyone figured out a fix?

Thanks for adding a screenshot regarding the problem you've encountered when connecting your bank to the system, Matt. I'm here to shed some details on how to get past this so you can continue managing the account and its data in QuickBooks.

The error code OL202, as stated in the attachment you've added, indicates that:

• There are several issues with your financial institution's end.
• Problems due to poor internet reception.
• Your details in the Financial Institutions Directory (FiDir) in QuickBooks need to be updated.
• There are complications with your bank accounts and file compatibility in QuickBooks.
• You're using a discontinued version of QuickBooks.

With that, several troubleshooting processes can help us handle the issue. Before we start, please ensure to:

• Save a copy of your company file and settle any pending transactions.
• Log in to your bank's website and check for pending alters or notifications.
• Have a strong internet connection, and your Windows firewall setup authorizes connections to QuickBooks.
• See if you get errors in the Bank Feeds Classic Mode. If none, indicate the file from your bank works best in this mode.

Step 1: Download bank feed transactions in a test company file. Doing so helps us verify problems with your bank's servers:

1. Open your QuickBooks and navigate to the File menu.
2. Choose New Company and then Express Start or Start Setup.
3. Establish the bank feeds for the account you're having trouble with. Then, download your transactions.
4. If there's an error, confirm the issues with your bank. Reach out to their customer care team so they can assist you with this matter. If none, proceed to the next step.

Step 2: Confirm if your bank data is compatible with QuickBooks. Please know that the program only supports files with the .qbo extension.

1. Log in to your bank's website using your regular browser.
2. Locate and download data from your bank in a .qbo format.
3. Import the transactions to QuickBooks.
4. If you're still having issues after initiating the steps, contact your bank so they can help you sort this situation accordingly.

Nevertheless, please follow steps 3, 4, and 5 from this link if you can seamlessly view and import your transactions: Fix OL and OLSU Bank Feeds errors in QuickBooks Desktop.

I'm also adding these resources you might find helpful once you need to reconcile your accounts and run financial reports in the system:

• Reconcile an account in QuickBooks Desktop.
• Financial reports - QuickBooks Desktop.

Ensuring you can manage your transactions and data in QuickBooks is one of our utmost priorities here in the Community. If you have additional concerns with your bank connectivity or need assistance with your reports, hit the Reply button. We're always available to lend a hand.

@matt- I would advise not going through the steps outlined in the previous post. Obviously the QB team member has not taken the time to review this issue.

If your feed used to work but has now stopped as per the error message, you are in the same boat as many of us. This appress to be a QB error that needs to be resolved with a patch update, etc. I understand there will be another update on October 25... but I am not holding my breath. Going through Ivan's steps will be a waste of your time.

-Scott

Just adding to the chorus here, getting the same error message others have screenshot. I have been successfully downloading Citi card transactions for YEARS. My other linked accounts are still working without an issues. I've read through all of this posts and this is, as it nearly always is, something that needs to be fixed on QuickBooks' end. I've been using Quickbooks for 20 years, and the usual trend is for Quickbooks to deny it could possibly be an issue, then there will be an update installed (FWIW, this current issue started after my most recent update), and then it will "magically" start working again. It's crazy making.

The feed is working again this morning. Yeah!  

I am still not working....again.... as of 10a, October 21

Oct 23rd... Still broken.

Just tried mine.  I'm getting the same error as of 10/23/24 11:20 am.  Hopefully QB will figure this out faster than they did the last time.  Like most of you, I have been downloading CitiCard transactions without issue for years, until this started.  I got if fixed for a while, now it's not working again.