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 the account directive & account metadata #217

Open
simonmichael opened this issue Nov 21, 2014 · 7 comments

Comments

Projects
None yet
2 participants
@simonmichael
Copy link
Owner

commented Nov 21, 2014

We want to add support for an account directive like Ledger's, to:

  • increase compatibility with ledger files
  • pre-declare account names, providing guidance and optional strict checking
  • define additional per-account metadata. For example, the account type (asset, liability, expense..)

julm has got the ball rolling on this.

Related:
Chart of Accounts support #50

An actual CoA would include every account that is relevant to you, whether or not you have any entries corresponding to each account. It should also be able to contain all desired details for each account; account number, bank branch addresses, terms, rates, paper-file cross reference, tax GIFI numbers, what have you. These details should not live in specific transactions, but they should be available wherever you need them; as reference to your chosen account structure and to enhance account-specific reports.

https://trello.com/c/uvwd6M8m/102-track-account-types-metadata-50
https://factor.cc/pad/p/hledger
http://ledger-cli.org/3.0/doc/ledger3.html#Command-Directives
http://plaintextaccounting.org/quickref/#h.3v5cafffbbft

Goals:

  • parse account directives, somewhat compatible with Ledger's, in journal files
  • allow account type (asset/liability/equity/revenue/expense) to be set in account directives (cf #523)
  • allow general account tags in account directives
  • enhance the accounts command to also show declared accounts and account tags
  • implement Ledger subdirectives: alias
  • decide how to align with Beancount's dated open directive


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@simonmichael simonmichael changed the title account directive, account metadata support the account directive, account metadata Nov 21, 2014

@simonmichael simonmichael added this to the 1.0 milestone Nov 21, 2014

@simonmichael simonmichael changed the title support the account directive, account metadata support the account directive & account metadata May 19, 2015

@simonmichael simonmichael modified the milestone: post 1.0 Oct 31, 2016

@mildred

This comment has been minimized.

Copy link

commented Apr 10, 2019

Would you accept a PR that implements the alias subdirective?

@simonmichael

This comment has been minimized.

Copy link
Owner Author

commented Apr 18, 2019

@mildred I've been away from this for a while but if you want to do it, yes I guess so. I don't have a feel for how useful it is compared to the existing alias directive.

@mildred

This comment has been minimized.

Copy link

commented Apr 18, 2019

Thank you, I wanted to learn Haskell a bit. The subdurective can be replaced by the alias directive, but when all accounts are declared up front it provides a better way to present the information.

There is something else, the alias directive ends at the end of file. This is a problem for me as I wanted to declare my account hierarchy in a separate accounts.ledger file included from the top level file. but the alias directives does not have any effect because of that. (See #1007)

Would it make sense to have the alias subdirective scope to continue after the end of file or not ?

@mildred

This comment has been minimized.

Copy link

commented Apr 18, 2019

If the account directive does not span past the end of file (as for alias) the previous comment makes no sense.

@simonmichael

This comment has been minimized.

Copy link
Owner Author

commented Apr 18, 2019

@mildred

This comment has been minimized.

Copy link

commented Apr 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.