Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for per-posting payee #2169

Closed
hieu-van opened this issue Feb 12, 2024 · 6 comments
Closed

Support for per-posting payee #2169

hieu-van opened this issue Feb 12, 2024 · 6 comments
Labels
A-WISH Some kind of improvement request, hare-brained proposal, or plea. journal The journal file format, and its features.

Comments

@hieu-van
Copy link

There are often cases that we might want to record payee on a per-posting basis. For example:

2024-1-2 an absurd transaction
        a:b:c                          $1     ; payee: Mr A
        a:b:c                          $2     ; payee: Mr B
        a:b:c                          $3     ; payee: Mr C
        wallet                        -$6

AFAIK this is possible with Ledger, but not with hledger. To achieve this, we can use a custom tag for recording payee, but that does come with its own limitations.

@simonmichael
Copy link
Owner

My 2c: this seems like a niche use case. When I have multiple payees, I usually feel separate transactions models that best. I have separate relationships/obligations with each of them which shouldn't be complected.

@simonmichael simonmichael added A-WISH Some kind of improvement request, hare-brained proposal, or plea. journal The journal file format, and its features. labels Feb 12, 2024
@hieu-van
Copy link
Author

You are right. We should hear about the others' opinion on this

@pwseo
Copy link

pwseo commented Jun 2, 2024

While I agree this would be a niche feature, it still seems like a good one because one can already do the same with the date: posting tag (it would feel more consistent if it were possible to do so with a payee: tag as well).
Ledger compatibility would also be a nice bonus.

@simonmichael
Copy link
Owner

simonmichael commented Jun 2, 2024

Consistency is a nice quality, but as de facto implementor/maintainer, (and given the level of complexity/legacy already in place,) you can probably understand if I'm reluctant to add complexity just for that, without solving practical problems.

Ledger compatibility is also nice but I have experienced that you can take that too far, we will never achieve 100% compatibility, and it is probably becoming less important for us over time.

But as always, a PR increases the chance that at least a few of us would give it a try.

@simonmichael
Copy link
Owner

simonmichael commented Jun 2, 2024

Something to ask ourselves: does this exist in double entry bookkeeping ? Is it something professional bookkeepers do ?

@pwseo
Copy link

pwseo commented Jun 2, 2024

Simon, I agree with you:

  • it probably makes more sense to split the transactions / it solves a single rarely occurring problem
  • adding complexity can harm hledger's ability to thrive
  • Ledger compatibility is less and less important
  • there are much more important things to do with your (maintainer) time

I was just providing additional reasoning that I didn't think was explicit in the comments above :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-WISH Some kind of improvement request, hare-brained proposal, or plea. journal The journal file format, and its features.
Projects
None yet
Development

No branches or pull requests

3 participants