Thanks community.
Sorry I wasn't clear, I agree beancount supports inline math, I was
refering to the missing support of the complex 'define' expressions by
ledger2beancount. I do not think that it makes sense to support them by
design in ledger2beancount when the ledger 'print' command is not
converting them (by design I believe, as printing is different than
reporting) and beancount also is not supporting them, again I believe by
design being beancount very good in extendability by python scripts. I
converted all of them in hardcoded values: they were merely 'nice to have',
nothing that could not be replaced by some notes in the transaction.
I also use virtual postings in ledger, to separate two different charts of
accounts: one aligned with my personal expense structure, that I recently
aligned with the national statistics for benchmarking, and one that allows
me to produce the tax statement in Germany using the EÜR numbers. As
virtual postings are not supported in beancount, these cannot be reported
using fava, but this should not be a problem as for this reporting ledger
report is robust enough.
Example (again using aliases) where I split the landline between home usage
and professional usage (allowed up to 20% in Germany), allocating an extra
virtual amount to the parallel chart of account used in the EÜR declaration:
2025-01-24 * 1&1 Telecom GmbH
home-landline (€37.98 * 0.8)
Expenses:Business:Landline (€37.98 * 0.2)
(EÜR-Pos:280) (€37.98 * 0.2)
bank €-37.98
I am now testing this hybrid workflow of using ledger for bookkeeping and
fava for analysis, bridged by ledger2beancount: I must say that it seems
complex but that might be attenuated by some hooks and automation. I will
post feedbacks here if this is something sustainable.
--Stefano
On Sunday, February 22, 2026 at 2:24:20 PM UTC+1 [email protected] wrote:
> * Stefano Merlo <[email protected]> [2026-02-12 07:15]:
> > I tried ledger2beancount but it does not support inline math.
>
> Maybe a nitpicky correction but it supports simple inline math.
>
> I don't see how complex expressions like yours could be supported
> as they are not supported in beancount. If there's anything
> ledger2beancount could do to make this easier, I'm open for
> suggestions but I don't see how.
>
> --
> Martin Michlmayr
> https://www.cyrius.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 visit
https://groups.google.com/d/msgid/beancount/f59699b7-d734-4e85-8b91-b5049a4b528dn%40googlegroups.com.
