Fidelity and missing transactions

Hi Kristina,

I double checked and the transactions are in fact sorted by date in ascending order. The 10 transactions in question are on the Fidelity website and are no longer pending. They are dated 9/15/2025. They should be at the bottom of the account register in Quicken (sorted by date ascending) but there is nothing more recent than 8/29/2025. There should be 5 interest income transactions and 5 principal payment deposits. There is a decent possibility that the transactions downloaded were identical to previous transactions but all of those are reconciled transactions and I would hope that Quicken would not match them to reconciled transactions without alerting me. This account was working flawlessly prior to the migration. No other transactions are missing as the reports through 8/29 match my month end reports that I printed prior to the migration. Every time I've reset or reauthorized the account since the migration, I've double checked the account number and the correct accounts were matched.

What I'm thinking is that something internal to Quicken thinks I've already accepted the transactions on that date and when they're received from Fidelity, they're skipped. I'm hoping there's a way to tell Quicken that they're new and need to be reviewed by the user.

Hello Kristina,

I'm going to wait until tomorrow to see if the 76 transactions that are currently pending in Fidelity come down. Hopefully they do and if so, I'll manually enter the 10 missing transactions unless you'd like the log files to try to head off this happening to anyone else.

Well, the 76 expected transactions did download. I checked the number of transactions waiting to be accepted and it said there are 76. When I accepted all, only 74 transactions made it to the register. I analyzed what was missing and found the missing transactions. There were 2 transactions for $0.80 and 2 for $0.62 which left me with a cash balance of $1.42 less than what Fidelity has. I'll have to manually enter those. I'll also manually enter the 10 missing transactions that started this thread.

This is a little off-topic so maybe it needs to be moved to a new thread but I've seen this curious behavior happen several times before and I had assumed that the fault lay with Fidelity in that they weren't preparing the download properly and never paid attention to there being a difference between the number of transactions downloaded and the number posted. I'm guessing there is some logic behind the "Accept All" button that attempts to recognize duplicate transactions and skips them when posting. If that's the case, I'd like to request that the process be modified to leave the assumed duplicates in the downloaded transactions list with some sort of flag indicating that they appear to be duplicates but giving me the option to accept them if I'm sure they're valid transactions.

To be honest, I didn't scroll the whole list so I can't say for certain. I do know, however, that all of the transactions already posted had been reconciled with a capital R. Would Quicken match a downloaded transaction with a previously accepted and reconciled transaction? Please say no.

"…should not…"

"…should have…"

I'd like to feel more confident but I guess that's a lot to expect. Thank you for the clarification.

If I entertain the assumption that some transactions are not mistakenly getting matched to reconciliated transactions, either Fidelity or Quicken is losing transactions in the online update process and I don't know of a way to determine which it is.