On Sun, Apr 29, 2018 at 10:17 AM, Einar S. Idsø <[email protected]> wrote:
> Justus and Martin, > > Sorry for my tardy response. > > On Mon, Apr 23, 2018 at 5:39 PM, Justus Pendleton <[email protected]> > wrote: > >> (...). If you don't want to see 100+ lines of clutter in your main file >> (which is totally understandable), create a "asset-transfer.bean" and >> #include that. (I think includes are an underrated and underused feature in >> beancount!) >> > > Thank you for the tip - that's a good way of removing clutter. > > If you aren't actually tracking which lot you transfer how do you possibly >> accurately calculate taxes? I know nothing about cryptocurrency trading -- >> and didn't quite understand the reasoning for why you aren't able to track >> your lots -- but in my experience with other securities either you or your >> broker HAS TO keep track of lots and tax authorities don't accept short >> cuts. Doesn't your broker do this for you? In another forum, I saw a post >> from someone who had several hundred thousand transactions (not crypto) in >> a single year and was able to track all of the lots. >> > > Sorry, I should have said that "it becomes /virtually/ impossible" to keep > track of lots since there is manual work involved. My broker keeps track > of tax calculations for my shares, but for crypto I am on my own to do the > calculations. It is not the volume itself that causes problems, but the > fact that 1) lots can be bought for one currency and sold for another, and > 2) when transferring lots between exchanges, FIFO is broken and I therefore > have to manually keep track of the lots instead of letting Beancount hande > it for me. That is why I am looking for a way to let Beancount handle lot > transfers between accounts. > > > Regarding linked accounts: After reading Martin's response and doing some > more thinking, I am not sure that linking accounts is such a good idea > after all. The idea was to link lots across exchanges in such a way that > whichever exchange you sell from, the cost of the first lot bought (FIFO) > is used to calculate PnL. However, the reduction needs to be from the lot > at the exchange where you sell, or else the total balance will be messed > up. So prices need to be somewhat disconnected from lots, or lots need to > be automatically transferred between linked accounts during a sale to > maintain balance. Either way it becomes rather messy and most likely > non-trivial to implement. > > On Tue, Apr 24, 2018 at 4:11 AM, Martin Blais <[email protected]> wrote: > >> The idea is supporting a transfer like this, simply moving the Position >> objects from one account to another while taking advantage of the booking >> mechanism for a reduction is a good one. I can see it being useful. It's >> not supported right now. I think this type of thing would require some sort >> of syntax. >> > > Great! Would this require modifications to the core, or can it be > implemented through a plugin? > I'm not sure, but I think it may require inserting code in the booking algorithms. Best is to try it out. -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhOFxfL6AineYmPELzr%3DArfguUeh4PtfV5UwUqSez4wgug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
