Continuing download errors in Quicken for Mac from Bank of Oklahoma

JayW

The problem with download errors from the Bank of Oklahoma continue. Without rhyme or reason, when some transactions download they DO NOT HAVE A POSTED DATE. There is no error message, just do no show a posted date. These are always with scheduled transactions. They are posted in the bank records, but not reflected same in Quicken for Mac IOS. I have talked with a "Mac tech" who tried to tell me that a posted date is not important (I guess another way of saying "ugh…I have no idea"). For my way of managing finances, a posted date in Quicken is extremely important. I was then told in a Chat session after it reoccurred that there was no way for me to contact support directly - only to post a problem hear (and I guess hope someone from Quicken that can investigate will read it).

jacobs

I was then told in a Chat session after it reoccurred that there was no way for me to contact support directly

@JayW Quicken chat support is Quicken Support. But if you didn't get a good resolution, it's often better to call and talk to Quicken Support by telephone, which allows for a better two-way conversation and allows the Support representative to screen share with you if it helps them understand or document the problem.

only to post a problem here (and I guess hope someone from Quicken that can investigate will read it).

That's not the way things work. This is a community forum, not an official Quicken Support channel. There are mostly fellow Quicken users here, along with a handful of Quicken moderators. In some cases, the moderators are able to report problems, but I'd suggest contacting Quicken Support by phone.

But let's go back to your actual problem withth your bank. I want to understand where you are seeing that a transaction has no Posted date. The transaction downloads and shows up in your register, so are you saying is has a Transaction Date, but not also a Posted Date? And you're looking for this in the Transaction Inspector window, which has a Date Posted field near the bottom? That field is under the section heading "From your financial institution", which is the raw data received from the bank without Quicken doing anything with it. If there is no Posted Date there, then your bank is not sending a Posted Date to Quicken in its transaction data. If that's the case, there's nothing Quicken can do about not because the problem is with the encoding of the transactions by the bank.

But you're saying these are all scheduled transactions? Do you have some transactions downloaded from the bank which were not scheduled transaction in Quicken, and those DO have a Posted Date?

It might help for you to post the Transaction Inspector window for one of the transactions (blacking out any data you consider sensitive).

Quicken Jasmine

Hello @JayW,

Thanks for your detailed post. I’ve reviewed both of your prior interactions and can confirm the information you received was incorrect. I’ve sent this to the appropriate teams for further coaching.

To clarify: when transactions download without a posted date in Quicken for Mac, it’s because that data isn’t being sent from Bank of Oklahoma’s servers. Quicken doesn’t have access to insert or correct posted date information—it has to come directly from the bank.

Since Quicken for Mac does not currently allow users to manually edit the posted date, one workaround for now is to hide the Posted Date column entirely and use the Memo/Notes column to enter the correct posted date for your own reference. This can help preserve your tracking workflow until the issue is resolved at the source. You can do so by navigating to the specific register > clicking Columns in the bottom right-hand corner > unchecking Posted and checking Memo/Notes.

I also recommend reaching out to Bank of Oklahoma and asking to speak with someone in their banking or aggregator department, as they are generally more familiar with how Quicken connects and receives data. They may be able to escalate the missing posted date issue internally.

If you'd like to see the ability to manually enter or edit the posted date in a future release, you're welcome to create an Idea post to suggest that enhancement.

Let me know if you need anything else!

Quicken Jasmine

https://community.quicken.com/discussion/7963246/continuing-download-errors-in-quicken-for-mac-from-bank-of-oklahoma

I haven't heard from you yet, just checking in!

JayW

My comment would be "Bank of Oklahoma says it is not their system, it is the Quicken now treats it." as if there has been a change. Trying to get someone who really can talk about this directly is nearly impossible. Unless someone from Quicken contacts someone from Bank of Oklahoma directly, this will never get resolved (which may ultimately force me to see other options). Why cannot Quicken take the lead on this and contact the IT support with Bank of Oklahoma (Tulsa headquarters) and try to get me out of the middle.

JayW

As another follow up, Quicken FAILED to download a rather significant action (one that actually involved my bank directly) resulting in overdraft. This situation is rapidly becoming unbearable. Quicken will do nothing about it and my bank finds no problem, and that leaves me in the middle on the outside. Extremely disappointed in the the assistance from Quicken "Support".

JayW

I have just spent 1 ½ hours on the phone with Quicken tech support and the final result is (drum roll please) - They don't know and have no solution (and this was from the higher level of support folks). "It must have been when the bank was having a problem". Nope. Again the user is caught in the middle with no other options than to find another financial software program. I will end this comment thread with the following note to users: Don't expect that Quicken support will solve all your problems, just some of them on occasion. By the way, the initial support tech (Jorge) was friendly and did the best he could, but the next level had no valid solution to my problem. Best wishes.

Quicken Jasmine

Hello @JayW,

Thank you for sticking with this and for sharing such a thorough follow-up. I want to acknowledge the frustration you’re feeling, especially after doing everything right—reaching out, following up, and investing your time on the phone with our support team. That shouldn’t go unrecognized.

After reviewing your recent call, I can confirm the issue with the missing transaction appeared to affect only activity on 6/10. As of now, downloads are functioning correctly, and no further connection issues have been identified. The account appears to be syncing as expected.

Just to clarify: the “missing transaction escalation” process is designed to address connection issues that are actively preventing Quicken from downloading transactions from the bank. That escalation helps us work directly with the financial institution or aggregator to resolve the root cause of the disruption. However, it does not recover historical data or any transactions that failed to download before the connection was restored. I know that can be deeply disappointing, especially when critical data is involved.

Since there’s no current connection issue to fix, the best course of action now is to manually enter the missing transaction(s) from 6/10 into your register. That ensures your account remains accurate and up to date.

I completely understand why you'd like Quicken to take the lead and work directly with Bank of Oklahoma’s technical team. Unfortunately, due to financial data privacy agreements and connectivity structure, our teams don’t have the ability to initiate direct contact with every bank’s internal IT group. That said, if Bank of Oklahoma believes the issue lies with how Quicken is handling the data, they are welcome to reach out to our connectivity partner directly. You can request they escalate this through their Quicken/Intuit support channel—banks do have those paths available.

I know this doesn’t solve the broader problem you’re seeing with posted dates and the occasional missing data, but I do hear you, and I’ll continue to track this internally. If you run into any additional problems or if you see this happen again, especially with future transactions, please let us know right away so we can re-escalate if needed.

Thanks again for your persistence and patience.