Beancount runs statistics on your inputs, and attempts to figure out the desired - tolerance (for balancing transactions and interpolation) - precision (for rendering numbers) In v3 this will get completely redesigned and better documented, it's a constant source of confusion. In the meantime I want to add a new option that allows you to set the tolerance and precision explicitly. It isn't entirely obvious because there are different parts of the code that render numbers (bean-query, reports, and the web interface) and they're in different states of using these precisions.
On Wed, Jun 3, 2020 at 9:40 PM James Cook <[email protected]> wrote: > I noticed that if I have any transactions with whole USD usd amounts, > both bean-web and fava start reporting balances with zero digits of > precision (e.g. -7 instead of -6.97). If I comment out those > whole-number transactions, I get two digits, probably because my other > transactions have two digits. > > Is that expected behaviour? If it's a bug, I'm happy to try to put > together a minimal reproducible example. > > I'm mostly asking because I don't see it documented anywhere, but if > there's a way to override it (e.g. with metadata attached to a > commodity directive) I'd be interested to hear. > > James > > -- > 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/CAHpmPOCDh%2Bc%3D4pdEWTS114%2BXg_Q%2B620sN4Cd3UhR-Uhoxhy-8A%40mail.gmail.com > . > -- 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/CAK21%2BhOTcmvBwV-ZMd6pDVwy56u034WS-Ad-8uyVm-zf-nCyLg%40mail.gmail.com.
