Balance issues with Capital One

RobWilk

The same issue i have with chase is currently showing for Capital One.

The problem in a nutshell:

The transactions total should equal $0

The website shows:

Quicken shows:

The $83.31 seems to come from these cleared transactions:

I suspect but do not know that in 4-6 hours at next sync it will be fixed.

p.s. sent feedback while it was broken if needed just now

-Rob

RobWilk

Please communicate this to product team or engineering preferred:

-The problem is in the amount "pending" in the tooltip on top right of account screen, it is not updating at the right time, it is delayed until the next sync at least

-The numbers for the pending there DO NOT COME FROM THE BANK, they come from the manually entered simplifi transaction entries - so if i enter a transaction manually for $123456.78, without touching the bank to sync, that pending amount will show $123456.78, and this affects the balance

-When the bank syncs, transactions that were manual/pending are properly being cleared, but the pending total on that tooltip is not reflecting the newly synced reality in the register.

Coach Natalie

@RobWilk, thanks for reaching out to the Community!

The first thing we'll want to do to troubleshoot any balance issues is to establish a completely fresh connection with the bank, as well as gain a new access token since Chase is one of our OAuth API banks. You may do so by following these steps:

1. Navigate to the bank's website, sign in, and remove Quicken's access from the bank's third-party linked apps.
2. Navigate back to Quicken Simplifi and make all of your accounts with this bank manual by following the steps here.
3. Once you see the account(s) listed in the Manual Accounts section under Settings > Accounts, go back through the Add Account flow to reconnect to the bank and reauthorize your accounts.
4. Carefully link the account(s) found to your existing Quicken Simplifi account(s) by following the steps here.

Once done, please keep an eye on things moving forward and let us know if the issue pops up for you. If it does, we can gather specific data and review your case for escalation.

We look forward to your reply!

-Coach Natalie

RobWilk

I did it.

I'm going through the motions and answering the questions as needed to help try to identify the issue.

I know the bank connection is not the issue, though, because it is not a bank-specific problem, plus all transactions are showing in the register properly.

-Rob

EL1234

@RobWilk do you see this with a CapitalOne checking account or savings account? Since I've got CapitalOne accounts in addition to Chase I'm thinking about initiating a transfer just to see what happens. (I mostly use Chase so haven't noticed the issue with Cap1 yet).

I agree with you that isolating the issue with CapitalOne makes sense, if we can get it fixed for all banks (one can always hope) then it'll be easier to pin down the Chase issue.

RobWilk

I briefly had a Capital One checking/savings account around 2021, but I only have the BJ's One credit card from Capital One. It's not a primary use credit card, though.

EL1234

Got it!

SRC54

I have Capital One Checking/Savings and so far have not seen this problem YET.

Checking will update the balance but not clear the pending. If I clear them myself, it goes back into balance. They clear the next download.

With Savings, sometimes it will download my interest but not update the balance until the next download. So that's wrong for a few hours.

I am pretty sure this is a bank problem since this behavior is the same in Quicken Classic and Simplifi. But since Classic adds everything up, I stay in balance there. I just get discrepancy warnings.

RobWilk

I am going to focus on getting Chase working, as that is my primary bank. As a result, I'm going to say you can "close" (maybe temporarily) this request, and I will not add more to it. I will repost if I decide that this is separate and still needs to be addressed.

It sounds like a fix is in the works for what I believe are the Chase Weekend Issues. It's also "possible" that this issue could be fixed by it or helped narrow it down.