Re: Long/short term tx splitting

2024-10-19 Thread Lover O'Bean
That does seem ignificant. It will be interesting to see if the increasing capabilities of ChatGPT will continue to be matched with increased availability of Sarco Pods for people whose skills become worthless. On Thursday, October 17, 2024 at 7:39:27 PM UTC-4 Red S wrote: > I needed pretty mu

Re: Long/short term tx splitting

2024-10-17 Thread Red S
I needed pretty much the same thing recently. Here’s a gist to build up capital gains data from Beancount, and output it in any format desired. The gist assumes a certain account structure to determine which

Re: Long/short term tx splitting

2024-10-17 Thread Red S
I needed something very similar recently. Here’s a gist to build up capital gains data from Beancount, and output it in any format desired. The code was almost completely written by GPT. On Friday, August 2

Re: Long/short term tx splitting

2024-08-23 Thread Eric Altendorf
On Fri, Aug 23, 2024 at 10:22 PM Red S wrote: > Why bother splitting it into two transactions? Why not just query by > postings with the held: "long" metadata? > For 8949, you're supposed to report the acquisition cost, disposal proceeds, and the delta (gain/loss). Separately for long-term holdi

Re: Long/short term tx splitting

2024-08-23 Thread Red S
Why bother splitting it into two transactions? Why not just query by postings with the held: "long" metadata? ​ On Friday, August 23, 2024 at 1:41:35 PM UTC-7 erical...@gmail.com wrote: 8949 annoyingly completely segregates short term and long term sales into separate tables. So if you had a

Re: Long/short term tx splitting

2024-08-23 Thread Eric Altendorf
8949 annoyingly completely segregates short term and long term sales into separate tables. So if you had a sale like in the example, you're supposed to split it into two sales, one which sells only the assets held for a short term, and the other which only sells the assets held for long term. I h

Re: Long/short term tx splitting

2024-08-23 Thread Red S
I forget what all 8949 needs, but metadata+querying (or a custom script) usually works well for these situations in my experience: 2016-03-01 * "Sell" Assets:Brokerage -100 ORNG {1 USD} @ 2.50 USD held: "long" Assets:Brokerage -100 ORNG {2 USD} @ 2.50 USD held: "short" Assets:Bank 500 USD Incom