Bug Can Bite When Same Security Held in Two Investment Accounts

No f-ing way are they the same EXACT same CUSIP's with different maturities.

You're trying to take a short-cut ... it didn't work ... and you're trying to blame it on Quicken.

Take some responsibility!

Perhaps your description left out some important information, but from what you posted, I do not understand why you think there is a bug. Do I understand you to say that you identified two different real-world securities as being the same security to Quicken ... then thought it was a bug that Quicken treated them as being the same security? Securities with the same ticker symbol get the same prices ... been that way since well before Q2004. I suppose that begs the question: why assign two different securities the same ticker symbol?

If you have securities that do not get assigned a ticker symbol in the real-world, you have a fairly wide range of choices for "dummy" ticker symbols you can use. Surely you can come up with a convention for assigning unique dummy ticker symbols to your securities when there is no real-world symbol available. I don't know how many securities of different prices can have the same cusip number or how many of those you are likely to own, but I would think you could find a much shorter suffix than the one you did for the purpose. A single letter of the alphabet might be sufficient.

You need to give the new bill a different ticker. For bonds, I've typically used "~Abbr1" "~Abbr2" or something like that. Change the "ticker" for the new bond, then edit-delete the purchase price data for it and re-enter correct price data. Since these are the same issue, you'll need to enter periodic price updates in two securities instead of one.

Alternatively, you can give them the same ticker, but different names: TBill20050415" and "TBill20050815" would be a way to distinguish them by purchase date. They become two different securities in your records.

Either way, make sure that the default purchase price is corrected to the actual purchase price in the register. This will only affect the other purchase on that date (which can be fixed by editing price info).

Deleting a security in Quicken does not delete it's price history. And if you later add a "new" security with the same ticker, it will get the same prices as were left in the price history for the deleted security. But you can delete those prices manually.