Simon Michael

To recap, the reason for changing things is to solve these problems: - hledger's transaction balancing (and journal reading) is quite dependent on display precisions; and more specifically, on commodity...

And this might justify a version jump to 1.50, signalling the unusual breakage ("Unfortunately it can also reject some journal entries that worked with older hledger"); I don't know.

And to recap more: the compatibility workaround I was contemplating was to offer a third option, `compat`, as the default: ``` --txn-balancing=... how to check that transactions are balanced: 'old':...

From chat: Q: does that mean, with the old approach, accounts can theoretically accumulate tiny errors over time? A: that kind of error does not arise, at least because we...

New doc: ## Transaction balancing How exactly does hledger decide when a transaction is balanced ? Especially when it involves costs, which often are not exact, because of repeating decimals,...

Thanks @mvhulten. I tried to suggest there should be at most "*one* amountless posting", I'll clarify.

A UX improvement: if it sees an unbalanced transaction that older hledger would have accepted, it adds an informative note. ``` 5 | 2025-01-01 | a $1.1206 | b $-1.120...

Thanks for the comments; this has been merged, and included in the https://github.com/simonmichael/hledger/releases/tag/nightly binaries.

I like the idea in general, though it sounds hard to provide good coverage when you think of all the banks in the world. It's related to setup, and perhaps...

Also related: https://github.com/simonmichael/hledger/issues/507, smarter/automatic CSV conversion