Thanks Dan, that makes a lot of sense and lines up with Ben's suggestion as
well. I think in my case I'll keep the income leg separate as well in an
"Income:Hooli:BIK" instead of adjusting the ":Salary" leg. This way I
retain the distinction between the "real" salary and the benefits, but
apart
Hello Pedro,
except the name, which I never heard before, I think this form of
benefits is rather common. The way I handle it is to simply record it as
an expense, ie the fact that the money never reaches my bank account is
not relevant for accounting purposes. The expense is recorded as a
posting
Putting it in Expenses makes a lot of sense. I was originally thinking
Equity since it's not an expense that you personally pay, but since it's an
expense incurred on your behalf it does make sense to attribute it to your
expenses. I'd want to make sure it was in a separate Expense account if it
we
That's what I was considering. I suppose that is the only way really: if I
want to report on it I need to record it as a posting and I need to absorb
it somewhere so everything balances.
Is there any reason you're suggesting an equity account as opposed to, say
expenses? Intuitively, it feels s
How about adding an Income leg for the BIK amount + an equity posting which
absorbs it? That will make the transaction balance.
On Fri, Feb 26, 2021, 10:02 Pedro F wrote:
> Hi everyone, I've been lurking here for a while as I migrated my 10 years
> worth of transactions into beancount (from a be
Hi everyone, I've been lurking here for a while as I migrated my 10 years
worth of transactions into beancount (from a bespoke solution involving
excel and python). I'm now fine tuning things and starting to extract nice
report and I'm really pleased with beancount/fava and what it can do,
incl
