Q2003 - problem with handling of a CD

This is a bit hard to describe.

  1. I set up a brokerage account some months back with a linked cash account.
  2. I downloaded transactions into Q2003.
  3. One of the transactions was for a "Problem CD" - this was transferred to me from an external account. Quicken made an entry into the linked cash account for the "Problem CD" with the face value showing as a deposit. In the linked investment acct., the "Problem CD" is entered with the same face value in the "Amount/Comm" field and "MiscIncX" in the "Action" field..
  4. New CDs bought with money from the linked cash account show up in the investment account as "BuyX". In the linked cash account, the face value is shown as a "Payment".
  5. In the "Security View", the "Problem CD" has 0 for "shares held" and
0 for "MktValue". The other CDs show a number in the "shares held" field and the face value in the "mkt value".
  1. When I do reports, I can track the new CDs as individual entities, but the "Problem CD" is invisible. It is just a part of the lump sum cash. For Example: CD 1 ,000 CD 2 ,000 Cash 5,000 (including the "Problem CD")

I want the "Problem CD" to act just like the other CDs, but I haven't the foggiest idea how to do it.

Does anybody have any idea what kind of transactions I have to do to accomplish this?

LC p.s. I have several reasons for doing this - mainly so my reports will contain the info I want and so it is easier to compare my Quicken stuff with the brokerage statements. But, in addition, Quicken keeps telling me (when I try to reconcile) that things don't match up and I think this might be one of the reasons.

Reply to
LCaution
Loading thread data ...

Have you tried changing the MiscIncX transaction to an "Add - Shares added" transaction.

Reply to
John Pollard

I just tried it and it doesn't work. Quicken gives a "doesn't match" message and asks me to adjust shares or cost basis. I tried both and, in both cases, the value in the investment account stays the same, but the value of the linked cash account is reduced by the amount of the CD

- so it results > LCauti> > This is a bit hard to describe.

Reply to
LCaution

I don't understand. What "doesn't match"? I tested in an investment account with a linked cash account; I had no trouble changing a MiscIncX to an Add Shares. But even if you can't "Edit" it, you can surely delete the MiscIncX and Enter an Add Shares from scratch. Since this sounds like a new "security" (CD), during the process, I would expect Quicken to drop you into the "New Security" dialog.

And I also don't understand your comment about the net loss. You said the CD came from a source you were not tracking in Quicken; so you didn't pay for it from your linked cash account or any other Quicken account ... so I can't understand why any transaction involving that CD should wind up *deposting* money in the cash account. (Probably the result of the fi not having anyway to know how you would want the transaction handled).

The way to introduce a security into an investment account when you didn't pay for it with cash from a Quicken account is to "Add Shares". And when you add shares, you can enter a "cost" of those shares; that should establish a "price/share", if the security is new; though you can also just add your own price in the price history.

When you finish, your investment account should have a value that is increased by the value of the CD (as entered by you), and the cash account value shouldn't change: as measured against the value of those accounts *before* the MiscIncX transaction was entered, not after.

Reply to
John Pollard

Thank you!

I deleted the CD transaction from both the investment account and the linked cash account. Then I added it back in with the Shares In, as you suggested. Once I got the #shares and price right, it worked!

I think, as you suspected, that the problem developed because the CD came from an account that wasn't in Quicken in the first place.

I very much appreciate your patience and good advice.

Reply to
LCaution

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.