Home Page link  

Security matching, revisited

 

Quicken Personal Finance Discussions - Quicken - personal finance software discussions

 Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Security matching, revisited Al 07-27-2008
Posted by Al on July 27, 2008, 6:37 pm
Please log in for more thread options
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. <SELLSTOCK> - have secname in MEMO
field.
** Holdings records - <STOCKINFO> - 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
<STOCKTYPE>OTHER
<ASSETCLASS>OTHER

I am tiring of "fixing" the "problem" and would appreciate knowing
what else beyond CUSIP is used in matching.

AL (QknDlx08,R7)

Posted by John Pollard on July 27, 2008, 9:11 pm
Please log in for more thread options
Al wrote:
> 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).

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.

> ** Qkn Help says investment transaction matching is by "the
> exact same
> name or ticker symbol"
> ** Investment transactions - i.e. <SELLSTOCK> - have secname
> in MEMO
> field.
> ** Holdings records - <STOCKINFO> - have secname & ticker
> listed as
> such.

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.

> 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
> <STOCKTYPE>OTHER
> <ASSETCLASS>OTHER
>
> I am tiring of "fixing" the "problem" and would appreciate
> knowing
> what else beyond CUSIP is used in matching.
>
> AL (QknDlx08,R7)

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.

--

John Pollard
First initial underscore Last name at mchsi dot com
Please reply to newsgroup



Posted by Al on July 28, 2008, 10:58 am
Please log in for more thread options
> Al wrote:
> > 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).
>
> 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.
>
> > ** Qkn Help says investment transaction matching is by "the
> > exact same
> > name or ticker symbol"
> > ** Investment transactions - i.e. <SELLSTOCK> - have secname
> > in MEMO
> > field.
> > ** Holdings records - <STOCKINFO> - have secname & ticker
> > listed as
> > such.
>
> 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.
>
>
>
>
>
> > 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
> > <STOCKTYPE>OTHER
> > <ASSETCLASS>OTHER
>
> > I am tiring of "fixing" the "problem" and would appreciate
> > knowing
> > what else beyond CUSIP is used in matching.
>
> > AL (QknDlx08,R7)
>
> 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. =A0See above.
>
> BUT: I suspect that there are certain security "types" that
> Quicken will not expect to download certain data for. =A0I'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. =A0 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.
>
> --
>
> John Pollard
> First initial underscore Last name at mchsi dot com
> Please reply to newsgroup- Hide quoted text -
>
> - Show quoted text -

Aha! No transactions for Market Index! Indeed! In the real world the
securities are equity funds/mix of equities assembled to follow/mimic/
whatever-the-financial-term-is an index of something-or-another
financial sector (industrials, housing,currencies,etc.).

Lesson 1: Just because something appears on a dropdown menu does not
mean it is applicable to one's case.
Lesson 2: Think first what you are trying to do in the real world
(paraphrasing RC White)

I'll reclassify/reselect/etc. and see where that takes me.

Thanks, John.

Similar ThreadsPosted
RESTORE revisited January 17, 2007, 4:41 pm
MS Mouse Scroll Wheel Problem - revisited August 13, 2007, 12:13 pm
revisited - Q2006 Rollover balloons in scheduled transactions May 22, 2006, 9:29 pm
downloading and matching September 20, 2008, 11:32 am
Matching downloaded transactions. August 26, 2007, 12:01 am
Manually matching transactions November 30, 2007, 12:32 am
Matching already downloaded and accepted transactions. August 19, 2007, 2:43 pm
Manually Matching - open transactions left over? September 20, 2008, 7:15 am
Quicken 2008 why must it download transactions for matching when using Billpay (Bill pay) March 3, 2008, 10:03 pm
Error in security value? October 27, 2006, 11:27 am

Contact Us | Privacy Policy
This site is not affiliated with Intuit - makers of Quickbooks and Quicken software
This site is not affiliated with Sage Software - makers of Peachtree accounting software
XML SitemapXML Sitemap