Re: Beware the downloaded investment transaction "Near Match" status.
John Pollard <[email protected]> Thu, 13 Jun 2024 07:40:13 -0500
| Newsgroups | alt.comp.software.financial.quicken |
|---|---|
| Organization | A noiseless patient Spider |
| Message-ID | <[email protected]> |
On 06/13/24 7:28 AM, John Pollard wrote: > On 06/12/24 9:52 PM, JohnA wrote: > >> Interesting that Quicken allows a match of a reconciled transaction. I >> would think reconciled transaction would not be a candidate for near >> match or match. Am I missing something? > The matching process for downloaded transactions does not consider the > Cleared Status of existing transactions, for good reason. > > The Cleared Status of a Quicken transaction is not a reliable indicator > that a transaction has been downloaded. > > If a user has been running Quicken manually (not downloading) for some > time and has reconciled transactions - then begins to download > transactions; there will be reconciled Quicken transactions that were > never downloaded. Those never-before downloaded transactions are > legitimate candidates to be Matched. > > Every downloaded transaction has a field known in Quicken as "Downloaded > ID": the Downloaded ID is required to be unique for every transaction > downloaded from the same online account to the same Quicken account. > > Quicken uses that Downloaded ID to determine whether a transaction has > been downloaded before. If the Downloaded ID for a currently downloaded > transaction is the same as the Downloaded ID for an existing Quicken > transaction, Quicken will just skip the currently downloaded transaction > - the user will never see it. My reply was incomplete. I forgot to mention that I think the Near Match transaction gets special treatment, since Quicken suspects that the downloaded Near Match transaction is the same as an existing Quicken transaction, but more "correct". Having said that, I tend to agree that - at least in the case of the original poster in the referenced Community discussion - since the user's existing transactions had most likely been downloaded, Quicken should not have treated the newly downloaded transactions as any sort of Match.