-
-
Notifications
You must be signed in to change notification settings - Fork 306
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
Comments
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. |
You are right. We should hear about the others' opinion on this |
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 |
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. |
Something to ask ourselves: does this exist in double entry bookkeeping ? Is it something professional bookkeepers do ? |
Simon, I agree with you:
I was just providing additional reasoning that I didn't think was explicit in the comments above :) |
There are often cases that we might want to record payee on a per-posting basis. For example:
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.
The text was updated successfully, but these errors were encountered: