Investment transactions

John Nastasi

Does anyone have a guide on how different investments transactions effect the Cash Balance and the Total market value. I'm having issues with Securities that have changed their name (ie. Facebook (FB) changing the name to META) which is causing a Securities Comparison Mismatch and I do seem to be able to resolve the problem. There appears to be a disconnect with the FB/META transaction flow.

A guide on how all the Investment Transaction work would be very helpful in fixing the problems. I've tried talking to Tech Support but they had no idea how to fix the problem.

Thanks,

NotACPA

Given that not only the company name changed, but also the ticker, I'd suggest using the Corporate Acquisition tool for a 1:1 acquisition of FB by Meta.

q_lurker

The change of name and change of ticker were actually two different events, though I am not sure that matters.

In my records, I simply changed the name and the tickers at some point in time. It is likely the CUSIP also changed.

In your case the security mismatch suggests a CUSIP disconnect. Fundamentally, that suggests you need to uncheck the box for the security about it being matched to an online security, and then let the next download create a proper match. Without knowing better how your securities currently show, it is hard to be specific.

Keeping all the FB and META transactions under one name assures continuity of balances and valuation but also deceptively shows you owned META when it did not exist.

Keeping two separate securities as NotACPA suggests means longer term performance needs to consider both securities at the same time, possible but subtly difficult.

Becomes a user choice.

John Nastasi

NotCPA, what is the " Corporate Acquisition tool for a 1:1 " you mentioned. Is it a function in Quicken?

Thanks

Jim_Harman

In an account where you hold the security, click on Enter Transactions and select Corporate Acquisition (stock for stock) and enter 1 in the New shares issued box.

John Nastasi

Thank you, I'll check that out.

John Nastasi

The problem turned out to be META did not have a CUSIP code to match the FB CUSIP. Once I got that resolved everything worked again.