On 02/03/23 19:28, fin wrote:
i'll figure it out eventually
now that i know the error is indeed something i did wrong
and not the error/rounding issue.
AFAIK there are never been bugs reported on Beancount regarding
inaccuracies due to rounding or other computing errors. The only issues
somehow related to rounding are about how Beancount decides how many
digits to display.
2000-01-01 * "Split 2 FOR 1"
input: "01/01/2000,20000101-001,Split 2 FOR 1,,INTC,,,,,,,"
transId: "20000101-001"
lot: "43.5 USD, 1999-01-01"
Assets:SB:WHS:INTC -25 INTC {43.5 USD, 1999-01-01} @ 43.5
Assets:SB:WHS:INTC 50 INTC {43.5 USD, 1999-01-01} @ 21.75
if i change that 2nd line to:
Assets:SB:WHS:INTC 50 INTC {21.75 USD, 1999-01-01} @ 21.75
or
Assets:SB:WHS:INTC 50 INTC {21.75 USD, 1999-01-01}
will that preserve the lot date? and will i have to reference it
by the new "21.75 USD, 1991-01-01" or would i still be using the
original "43.5 USD, 1999-01-01"?
I think the question is not well posed. Lots are identified by cost,
date, and an optional label. If no date is present in a cost
specification, Beancount uses the date of the transaction. Lot are
merged only when all these three attributes are the same. See here
https://beancount.github.io/docs/how_inventories_work.html#cost-basis
Therefore, if you change the cost, from the Beancount point of view, you
have a different lot. I think this behavior is the most intuitive one.
Cheers,
Dan
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/310ae6d5-dedf-26d5-435e-e0c601b34a72%40grinta.net.
