Dumb question on determining cost basis

[pps8888]

Really dumb question, but I must be missing something....ran the tool, all good have the output file.

Which column will give the new cost basis for the AVGO shares going forward? I have not sold any of my AVGO shares post merger.

Is it column M (per share avgo cost basis) or is it column O (per share cost basis)?

thanks

[wligithub]

Sorry for the late response, somehow missed this message. It is "per share avgo cost basis" for converted avgo shares sold from that log.

[pps8888]

Thanks much appreciated! Great work on this tool!On Jan 26, 2025, at 4:36 PM, wligithub ***@***.***> wrote: Sorry for the late response, somehow missed this message. It is "per share avgo cost basis" for converted avgo shares sold from that log. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[usmanajmal]

Consider following example from the output text file from 2024:

---------------------- row: 5 ------------------------------------
type: RS
share: 32.000
acquire date: 05/01/2021
merge or sold date: 11/22/2023
long term: True
Box 1d Proceeds: $2,186.36
Filing Cost Basis: $504.46
Total Capital Gain: $1,681.90
avgo share: 4.198
total avgo cost basis: $4,111.94
per share avgo cost basis: $979.50

per share info:
purchase price: $160.83
cost basis: $144.25
merge gain: $52.56
capital gain: $52.56
acquire date: 05/01/2021
acquire date fmv: $160.83

Since AVGO stock split 1:10 later, is it right to change that lot numbers to the following for future:

---------------------- row: 5 ------------------------------------
type: RS
share: 32.000 <------ What is this?
acquire date: 05/01/2021
merge or sold date: 11/22/2023
long term: True
Box 1d Proceeds: $2,186.36
Filing Cost Basis: $504.46
Total Capital Gain: $1,681.90
avgo share: 41.98 <------ Multiplied by 10
total avgo cost basis: $4,111.94 <------ This should stay the same
per share avgo cost basis: $97.95 <------ Divide by 10

per share info: <------ What is this for? Is it for the original Vmware share? Do we
need the following if we sell any of AVGO shares acquired due
to the acquisition?
purchase price: $160.83
cost basis: $144.25
merge gain: $52.56
capital gain: $52.56
acquire date: 05/01/2021
acquire date fmv: $160.83

[1porter]

Consider following example from the output text file from 2024:

---------------------- row: 5 ------------------------------------ type: RS share: 32.000 acquire date: 05/01/2021 merge or sold date: 11/22/2023 long term: True Box 1d Proceeds: $2,186.36 Filing Cost Basis: $504.46 Total Capital Gain: $1,681.90 avgo share: 4.198 total avgo cost basis: $4,111.94 per share avgo cost basis: $979.50

per share info: purchase price: $160.83 cost basis: $144.25 merge gain: $52.56 capital gain: $52.56 acquire date: 05/01/2021 acquire date fmv: $160.83

Since AVGO stock split 1:10 later, is it right to change that lot numbers to the following for future:

---------------------- row: 5 ------------------------------------ type: RS share: 32.000 <------ What is this? acquire date: 05/01/2021 merge or sold date: 11/22/2023 long term: True Box 1d Proceeds: $2,186.36 Filing Cost Basis: $504.46 Total Capital Gain: $1,681.90 avgo share: 41.98 <------ Multiplied by 10 total avgo cost basis: $4,111.94 <------ This should stay the same per share avgo cost basis: $97.95 <------ Divide by 10

per share info: <------ What is this for? Is it for the original Vmware share? Do we need the following if we sell any of AVGO shares acquired due to the acquisition? purchase price: $160.83 cost basis: $144.25 merge gain: $52.56 capital gain: $52.56 acquire date: 05/01/2021 acquire date fmv: $160.83

Did you get an answer to this? I am looking to get out of AVGO soon, including these long-held shares. Etrade shows a cost basis of zero, which is not correct. This tool is matching up nicely but it does not account for the split. I think your suggestions are correct when aligning with post-split etrade transaction dumps. maybe an update to the tool to add post-split fields? we can't be the only long holders out there.