-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
add support for per-account booking method override #268
Comments
OTOH, I don't like introducing meaning that doesn't exist in ledger. OTOH, I like it when ledger and beancount can be used in parallel with l2b and this helps with that (if it's a one time conversion, you could just add the booking method manually). |
Sorry for the delay. Do you still need this feature? I think it's ok to add. I can look into it if you still need it. |
I personally don't need it any more. (But might need it in the future.) |
Beancount has support for per-account booking methods, with the following syntax:
It would be nice to support for this in ledger2beancount.
Currently, the only workaround possible is quite awkward, as one has to disable automatic declarations for all accounts, and replicate manually all open directives with l2b blocks.
How to support it properly is debatable. My take: require a dedicated account metadata field (overridable with an option or otherwise) and interpret it as the booking method, e.g. (in ledger syntax):
The text was updated successfully, but these errors were encountered: