Al, FYI, pp263-264 of this merger document indicate that it is a
"reorganisation" and not a capital gains event.
https://www.sec.gov/Archives/edgar/data/2488/000119312521071625/d83168d424b3.htm#rom83168_22
However it also states:
"ALL HOLDERS OF XILINX COMMON STOCK SHOULD CONSULT THEIR TAX ADVISORS AS
TO THE PARTICULAR TAX CONSEQUENCES TO THEM OF THE MERGER, INCLUDING THE
APPLICABILITY AND EFFECT OF ANY U.S. FEDERAL, STATE, LOCAL, NON-U.S.
INCOME AND OTHER TAX LAWS."
Regards
Geoff
=====
On 19/02/2022 3:15 pm, Al wrote:
Geoff wrote:
Hi Al
We need to tweak your transactions to fix the cost basis on the
Advanced Portfolio Report.
Also from a tax accounting perspective, there are two ways to treat
this merger, depending whether it realised a capital gains event or
not. I'll cover both scenarios from a GnuCash perspective, but please
note that I am not an accountant.
Many thanks Geoff, the information that you provided will be quite helpful.
I'm waiting a bit on tweaking the transaction until I find out the
capitol gain status, although I am fairly sure that there is no capitol
gain other than the .72 fractional share amount. I'd just like to see
that in writing before committing the transaction.
Al
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
