-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Determine parameters around legitimacy of opting out of the pro-rata approach #13
Comments
From the merger agreement, section
I read this as, for any given shareholder, the ratio of shares receiving cash/stock consideration across their holding must conform to the ratio for the merger as an entirety. The specifically relevant section for tax treatment is |
The wording in form 8937 is weird, and leave a lot of room for interpretation. For instance, the other 8937 specifically state the boot + target share(s) received per source share (e.g. with wording like "each {source} share ... to {x} {target} shares, {y} cash" (e.g. AT&T and Time Warner Inc. form 8937) In our case, it did not mention something like "per share of VMW to ...", but only "the right" to convert 1 share of VMW to $142.5, or 0.2520 shares of AVGO. (See below) It is extremely intriguing why they worded so differently than other form 8937. """ |
Interesting, this form 8937 has similar wording as ours, but layout very clearly the tax rule (each block, apply sec 356 / 358 : recognize gain but not loss and adjust basis) |
if we set k26 of first sheet to "Manual per-lot ratio", and on RSU/ESPP sheets set each of the lots individually as cash or shares, and the accumulation of shares(converted) matches Total_Share * 0.520866, I can see the tax was reduced significantly, but the question is, would this be a legit approach to fill out our tax-return? |
@cwei44 answering that is the purpose of this issue. I've spoken to several people trained as CPAs (but engaged as one by me) and they've said that lot selection is a valid method. However they were unable to comment on whether there are any restrictions on who/how/when it's valid. Finding a CPA who:
is one of my primary goals. It's proving challenging. |
Added this analysis of merger sections 356 and 358 to the repo. Very informative, but still need assistance in interpretation. |
There's this section of IRS code ( §1.358-2(a)(2)(vii) ) which notes the basis assignment can be done at any point before it becomes tax-relevant. Not sure what that means for the fractional share and the lot it comes from - sale/disposition is definitely tax relevant. Not sure what else is. |
I recently transferred my shared from etrade to morgan stanley, and found all the tax lots are still there, i think this can indicate that all the lots were applied 48/52 as cash/convert ratio. so meaning i have to use "balanced". |
@cwei44 Lots are a mechanism for grouping fungible electronic shares. I would not have expected them to be lost in the transfer because the acquisition date, basis value, and whether it's covered/non-covered need to be preserved. That's distinct from saying, "this is how I'm applying the transaction across my lots". The purpose of this issue is to track whether choosing an assignment other than what eTrade decided is defensible. |
https://www.irs.gov/pub/irs-pdf/p550.pdf 65-66 Cost Basis
|
Depends on #10 - not worth pursuing this if it's a noise level effect.
The VMW f8937 is vague:
Thanks to Eric Leung for the references!
Details for historic precedent
The cost basis calculation is referenced in Code Sec. 356 (and 358):
Analysis from a NY law firm on this issue:
Back to Basis
Code_Sec_356_and_358_Regulations
April2006StockBasis
TLDR; "did the M&A agreement specify written down how to allocate basis or boot", and IRS won.
For VMW this seems relevant:
However the f8937 for VMW/AVGO is extremely vague. Counter-example that is very clear.
Even more explicit example f8937
VMW 8937 is more vague:
"the terms of exchange provide otherwise" mean we have to go back to the M&A agreement to figure that out.
And I remember the M&A agreement is equally vague.
The text was updated successfully, but these errors were encountered: