How do I fix a very obvious cost basis error?
Options
michael7572
Member ✭✭✭
JPMORGAN TR II - LIQUID ASSETS MONEY MKT FD INVSECU QABKQ
Everything has been sold. When I look through the activity it shows small $$$ in and out. However, the cost basis is showing as $92,233,720,368,546,728.85
This value was originally tied to one specific sale. When I went in and re-selected the First In the value went away. However, it just moved to the top alongside the JPMORGAN TR II but not linking to any specific sale.
Validate & Repair seems to see this but at the end says that "the value is too large." I'm assuming this is the value that's too large.
I could delete the entire TR II since it's now empty, but I'm afraid the problem will simply move elsewhere in that account.
Everything has been sold. When I look through the activity it shows small $$$ in and out. However, the cost basis is showing as $92,233,720,368,546,728.85
This value was originally tied to one specific sale. When I went in and re-selected the First In the value went away. However, it just moved to the top alongside the JPMORGAN TR II but not linking to any specific sale.
Validate & Repair seems to see this but at the end says that "the value is too large." I'm assuming this is the value that's too large.
I could delete the entire TR II since it's now empty, but I'm afraid the problem will simply move elsewhere in that account.
1
Best Answer
-
You can search this site for the 92-quadrillion problem and find a few applicable solutions. Fundamentally, you probably need to delete and re-enter some applicable (difficult to determine) transactions.
One solution I recall involved creating a second similar security, editing the transactions to refer to the mew version of the security, then deleting the old (problematic) security.
HTH5
Answers
-
You can search this site for the 92-quadrillion problem and find a few applicable solutions. Fundamentally, you probably need to delete and re-enter some applicable (difficult to determine) transactions.
One solution I recall involved creating a second similar security, editing the transactions to refer to the mew version of the security, then deleting the old (problematic) security.
HTH5
This discussion has been closed.