On Sat, May 4, 2019 at 5:45 AM Alen Šiljak <[email protected]> wrote:
> My real problem is that I have lots of small purchases over the years, and > then one big transfer to another account. I believe most of my "sales" so > far were due to funds, banks, and brokers going out of business. > So now I need to make decent adjustments to the source file to match the > positions on those transfers or sales. I actually wish Beancount was > already at the stage where it was bare bones flexible as ledger and all the > constraints were introduced by plugins. With a default set of plugins it > would be what it is today. > However, this would allow me to remove a few constraints until the source > data is corrected. > You can achieve precisely this by setting the booking method from "STRICT" (the global default) to "NONE". The NONE booking method disables booking constraints and devolves more or less to what Ledger does (only the total cost basis or number of units over all trades is meaningful). You can set this per-account (see Open directive) or globally (option "booking_method"). Regarding the repricing, it is a rabbit hole. It would be great to have > something like an effective date. For example, a stock is bought @ 10 in > January and split 2:1 in July. The reports for February would still show > the cost basis of 10 and the unrealised gain/loss based on February prices. > But as of July it would use the new cost basis and the number of shares. > However, for tax purposes, the positions still keep the January date. > Perhaps this is already possible. > If you "close" a time period for reporting (read this intro doc to find out how I've mapped this concept to transform a stream of directives into a shortened one: https://docs.google.com/document/d/100tGcA4blh6KSXPRGCZpUlyxaRUwFHEvnz_k9DyZFn4/edit#heading=h.uqoebvl2qxjs) the February report should show the same thing regardless of what is inserted after that date. > > -- > 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/bf3d4fec-0238-47c1-913f-392c659e872f%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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%2BhMvSD%3DW5TQi-NL5Sg8Un6-MGqfTN%3Dsvjw-kMAiY5P65QA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
