FI downloads continue to create duplicate entries of a couple of securities. (See "Security Foul-up" thread in this NG)
BACKGROUND:
** John Pollard said some time ago that [2005] matching is based on CUSIP # (not currently visible/editable in Quicken by users).
** Qkn Help says investment transaction matching is by "the exact same name or ticker symbol"
** Investment transactions - i.e. - have secname in MEMO field.
** Holdings records - - have secname & ticker listed as such.
QUESTION: Does the security type ALSO play a part? I have consistently classified the confounded securities as Market Index type and Mixture asset class, while the "new" securities appear IN QKN initially as Stock type and Unclassified asset class. The QFX file has them listed as OTHER OTHER
I am tiring of "fixing" the "problem" and would appreciate knowing what else beyond CUSIP is used in matching.
I'm not sure that I phrased my evaluation clearly ... I can't remember the post(s).
Ultimately, Quicken (and, I think every PSM app) matches downloaded securities by CUSUP #.
I think the key to the process is the initial "match".
The first time you download a security that you have never downloaded before, Quicken doesn't know whether that very specific security already exists in your Quicken file, or not.
So Quicken wants you to identify the security ... is it the same security you already have "added" (please remember the quotes) in Quicken ... or is it a "new" security that does not now exist in your Quicken data.
It doesn't really matter how any existing Quicken security is "identified" by anything other than CUSIP number.
Remember: you can no longer tell Quicken directly what the CUSIP number of a security is: the only way to tell Quicken what the CUSIP number of a security is ... is to tell Quicken that a downloaded security had the same CUSIP number as an existing Quicken security, or that a downloaded security is a NEW security, so Quicken will create a new security with the CUSIP number of the downloaded security.
If you tell Quicken that a downloaded security "matches" a security already in your Quicken file ... Quicken will assign the downloaded CUSIP number to your existing Quicken security ... insuring that forever after, the two securities will be seen as the same security ... even if they are not the same security.
At this moment, I can not think of a single time that Quicken has considered the security "type", when trying to "identify" a downloaded security. See above.
BUT: I suspect that there are certain security "types" that Quicken will not expect to download certain data for. I'm not certain I know what your problem is, but I definetely think that Quicken will - internally - treat security types, such as Market Index, differently than other security types.
Example (my apolgies; I have to run now): I don't think that Quicken will treat "transactions" for "market indexes" the same as it treats other transactions. I also don't think you should expect to classify any security as a "market index" if you expect Quicken to treat it as a "real" security.
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.