>>> "TP" == Tobias Pfeiffer <[email protected]> writes:

> Hi,
> sorry it took a while.
No worries, I am quite busy myself..

[Snip]...

Thanks for this explanation.

>> I wounder that this common situation is so hm difficult to achieve


> However, my understanding of double-entry accounting is that it is
> usually used to manage finances of *one* entity. There is an inherently
> one-sided view of writing things down, credit and debit flip meaning
> (or sign) once you view from the other side. I am not sure how well
> this way of writing things down works when you want to describe a
> "global state" of things, rather than the view from one single entity.
> This is what I meant when I said "somewhat contrary to the idea of
> double-entry accounting".


I see, that make sense.

> across participants. (This would be similar to apps like Kittysplit <
> https://www.kittysplit.com/en/> where each expense of one user is split
> between participants and then settled at the end. Note that settling
> expenses is not a trivial problem once more than two players are
> involved, cf. <https://stackoverflow.com/q/877728/3663881>)

Very interesting thanks


> You could also model this from the perspective of one of the involved
> users. Rather than keeping the expense as a whole and splitting the
> income side of things in automated transactions so that it becomes

[Snip]...


> Even though in the global view of things, flowers for 20 EUR and a tree
> for 140 EUR were bought, in your expenses account only your share of
> things ever shows up, not the total price. I think this may be much
> simpler, but you don't have the total overview of what was paid or
> whether a credit card was used by User2 etc.

Right this is why I stick to your solution, thanks again.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" 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/ledger-cli/871r1cdezi.fsf%40mat.ucm.es.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to