On Wed, May 22, 2019, at 11:43,
freak...@gmail.com wrote:
>
> Hi,
>
> I'm new to beancount and currently assessing whether I can switch from
> ledger-cli in order to make use of the web interface fava.
>
> I'm interested in ways on how to split expenses in beancount: I share a
> household with my partner and for many expenses I'd like to register
> only half the debit as a personal expense whereas the other half should
> be registered as an asset (something that my partner owes me).
>
> I currently use ledger-cli and make heavy of the following automatic
> transaction to split transactions with my partner:
> `
> = tag("With") =~ "Susa"
> $account -0.5
> Assets:Receivable:Susa 0.5
> `
>
> Shared expenses are then recorded like this:
> `
> 2019/05/22 * Bakery
> Expenses:Food 10.00 EUR ; With: Susa
> Assets:Cash
> `
>
> This results in a credit of 5.00 EUR to Expenses:Food and
> Assets:Receivable:Susa each. I find this quite comfortable and want to
> know if there is something similar in beancount. (I've already learned
> that there are no automatic transactions in beancount)
>
> I skimmed the documentation of beancount for sharing expenses and what
> "special" accounts (e.g. Expenses:Food:Fred & Expenses:Food:Susa) in
> order to split transactions using a plugin
> ("beancount.plugins.split_expenses") -- is this correct?
>
> Does the mentioned plugin work in way like the automatic transaction in
> ledger-cli does, i.e. does running beancount automatically split the
> written amount in the journal file or does the workflow involve running
> a command that results in hard-coded input text that replaces the
> original input data?
>
> More generally: How do beancount users normally record regular shared expenses?
>
> Thanks and regards,
> Fred
>
> --
> 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
beancount+...@googlegroups.com.
> To post to this group, send email to
bean...@googlegroups.com.
> To view this discussion on the web visit