nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

First Bank of Colorado Download not working again

James Young

Quicken for Mac 26.3.1 , Mac OS Tahoe 23.1 (a)

There have been various issues on the bank and Q end. It was resolved and working until 4/11/26. Now it is not working. Have tried several times to reconnect and keep getting QFX Error 16503. Assistance would be appreciated.

Find more posts tagged with

Online Banking

Mac

Comments

Quicken Anja

Hello @James Young,

Thank you for reporting this!

The OFX Error 16503 generally means Quicken is not receiving the expected response from the financial institution’s servers when attempting to download transactions. This can happen for a few reasons outlined in our support article:

Temporary server issues on the bank’s side
Online services not being fully or correctly configured for the account
Login credentials or connection settings being out of sync
In some cases, a mismatch between enabled services (such as Bill Pay) in Quicken vs. what is actually active at the bank

It’s also worth noting that even if you can successfully log into First Bank of Colorado through their website, Quicken may still fail if the server endpoint used for transaction downloads is experiencing issues.

Since you mentioned the connection was working and then stopped again after 4/11/26, this strongly suggests a temporary change or instability on the bank’s connection side.

At this point, the recommended steps are:

Wait 24 hours and try again (these errors are often temporary)
If the issue persists beyond that, contact the bank directly, as Quicken does not have control over their server responses

Additionally, please note that we do have this active Community Alert regarding a known issue with First Bank of Colorado. While the error listed there differs from what you’re experiencing, it may still be related. At this time, we do not have an ETA for resolution, but any updates will be posted to the Alert as they become available.

Thank you!