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; } } }

Unable to download UBS - Now have ERROR Code 16503

HawkeyeEyes

Now getting Error 16503 on all UBS Accounts.

3 convo w/UBS Support, the OFX file is correct. We have reset passwords, reset UBS OFX account authority, restarted computer, verified account names.

NO recent software upgrades for any devices

READ article saying to turn off BILL PAY in account settings. Like others said, I dont have that option displayed

[Removed Screenshots for Privacy & Security]

Find more posts tagged with

Online Banking

Mac

Comments

Quicken Anja

Hello @HawkeyeEyes,

Thanks for the detailed rundown of what you’ve already tried—that’s helpful, and I know this has been frustrating.

Error 16503 generally means Quicken isn’t receiving the expected response from the financial institution’s OFX server, even when credentials are correct, and website access works normally. This aligns with what you’re seeing, especially since the error is now affecting all UBS accounts.

You’re correct that one common cause can be Bank Bill Pay being enabled in Quicken when it isn’t actually supported or active on the bank’s side. If you’re not seeing a Bill Pay tab at all in Account Settings, that typically indicates the account isn’t enabled for that service in Quicken—so there would be nothing to toggle off in that case.

At this point, since:

credentials and OFX authorization were reset,
there are no Community Alerts indicating a widespread outage,
and the issue persists across multiple attempts,

the next step outlined in this support article applies: UBS will need to review this on their end as we do not have access to the financial institution's servers to correct the problem. They may need to check the server Quicken connects to, which is separate from standard online banking access.

If UBS is unable to assist at that level, asking for escalation within their support team is recommended.

Thank you!

HawkeyeEyes

Thank You

Quicken Anja

https://community.quicken.com/discussion/comment/20535204#Comment_20535204

You're welcome!

OldSchoolExec

I am currently seeing this issue as well. Same problem occurred last weekend after UBS did a maintenance shutdown. This and other issues with Quicken are a recurring problem at UBS. They never know when there are Quicken interface issue with their system and typically try to blame Quicken for the problem. Extremely frustrating.

bird

I ,also, am experiencing this issue. Problem report submitted. Just started on Feb 1.

Amperlative

Same issue from the past 2 weeks. Tried deactivating and reactivating. Bill pay is not activated, so that's not the problem. UBS says its not a problem at their end…quicken indicates it is UBS. No resolution

Ivan36

I suggest you delete the app, if that's what you're using, and reinstall a fresh version. Seems to help.

Quicken Anja

Hello All,

Thank you for taking the time to report this issue!

We have forwarded this issue to the proper channels to have this further investigated.

Thank you to those who have already submitted log files. However, for those who haven't yet, we request that you please navigate to Help > Report a problem within your Quicken program and submit a problem report with log files and screenshots attached in order to contribute to the investigation.

It would also aid the investigation to include a sanitized file when submitting the problem report. A sanitized file is a data file that removes personally identifiable information so you can comfortably share this file with the Quicken team.

While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.

Please let us know once you have done so!

We apologize for any inconvenience in the meantime! Thank you.
(CBT-1017/CTP-16212)

Ivan36

Following up… restoring the app helped but the problem persists. So I've been updating the app at least 3 times in a row to clear the problem, which works but only temporarily. It's still an ongoing issues.

Quicken Anja

@Ivan36 Thanks for the follow-up and for sharing your experience. We're glad to hear you found a workaround by temporarily restoring or updating the program.

Since this issue has already been escalated and is being investigated internally (CBT-1017/CTP-16212), at this time, there isn’t a new workaround beyond what you’ve already tried. Our teams are actively working on this.

We appreciate your patience!

de00304

I have had this issue since Jan 24. I have submitted logs to Quicken twice with no response from Quicken as to what they found. As such I can only assume they have not reviewed those logs. I have escallated to UBS support and UBS (to their credit) independently asked me to provide them the Quicken OFX log file - they analyzed that file and indicated that the issue was on the Quicken side and said that they have escalated it to Quicken support. Like others have reported, I also can get it to work if I keep trying to download over and over, but I do not consider this a "workaround" as I have no confidence that the results obtained this way are valid. I do have bill pay, but I have had that activated for over 20 years so that can't be the issue. I have deactivated/activated the download service on both sides (Quicken and UBS) and besides having to clean up duplicate transactions as a result, it has not resolved the issue. Note that I download UBS transactions to other services like Empower and Tiller and there are no issues with those.

This is beyond ridiculous, and at this point I am holding Quicken support fully accountable to get this resolved. Quicken: you NEED to get UBS on the phone along with users who can recreate the problem at will in real-time in order to get this resolved. Having an open issue for a month and asking the users to "be patient" is not cutting it anymore…

Quicken Anja

Hello @de00304,

Thank you for taking the time to provide such a thorough update and for sharing your experience. I completely understand your frustration.

I want to assure you that this matter has already been escalated internally (CBT-1017/CTP-16212) and our teams are actively working with UBS to investigate and resolve the underlying cause. While I know the repeated download attempts are not a true workaround, your detailed reporting and persistence help the team pinpoint the behavior and reproduce it in real time.

We appreciate your patience as the investigation continues!

Quicken Anja

Hello again to you all,

I wanted to provide an update on this issue (CBT-1017/CTP-16212).

Our teams have reached out directly to UBS Financial Services Inc. regarding the Error 16503 connection failures. At this time, we have not yet received a response from their technical team.

To help move this forward, we’re asking affected users to please do the following:

Contact your UBS advisor and explain that you are receiving Error 16503 when connecting via Quicken.
Ask your advisor for their direct email address and share that with us (do not post it publicly in this thread, just respond letting us know you have it and I will reach out to you via DM to collect it from you securely). This way, our teams can reference a specific contact.

Contact UBS’ technical support team directly and request that they open a case regarding the OFX/Quicken connectivity issue.
If they provide a case number, please share that with us.

The goal is to ensure the issue is escalated internally on the UBS side and routed to the correct technical team so they can respond to our teams. Direct pressure from clients often helps prompt faster engagement from financial institutions in situations like this.

We understand how long this has been ongoing and truly appreciate everyone’s persistence and detailed reporting. We will continue pushing on our end as well.

Thank you again for your patience!

Quicken Anja

Hello everyone,

Following up regarding the Error 16503 issue with UBS accounts. According to information shared in the escalation ticket, UBS Financial Services confirmed that the issue was resolved in early February, and verified that no errors have been recorded on their side in the past few days.

Please reply to this thread to confirm your current status:

If you are still experiencing the error, submit a new screenshot and a new set of logs via Help > Report a problem so our team can investigate further.
If the issue is no longer occurring, please let us know so we can mark it as resolved on our end.

Your confirmation is important to help us ensure the issue is fully addressed.

Thank you!