PTA is more or less a collection of formats. Beancount, for example, uses a colon-separated account name per transaction line, such as "Income:Work:PrimaryJob:HolidayAllowance" (excluding the quotes). There are a couple of fixed main accounts (such as "Income"), and the user can arbitrarily define subaccounts (in this example "Work:PrimaryJob:HolidayAllowance").
Although I see your point in wanting clarity, if the format supports arbitrary subaccounts, you can use the tool itself to limiting the number of subaccounts to show (e.g. with 1 you would only see the accumulated amount in all accounts in the "Income:Work" hierarchy). This still fits your use case for clarity, but allows other users to expand the budgeting tool to their needs.
Comments
I was just checking it out.
Nice, I missed that. I'll consider making it PTA-compatible!Only issue I have is with the indentation-based subitems.
I'd rather keep it restricted to top-level groups for clarity.
PTA is more or less a collection of formats. Beancount, for example, uses a colon-separated account name per transaction line, such as "Income:Work:PrimaryJob:HolidayAllowance" (excluding the quotes). There are a couple of fixed main accounts (such as "Income"), and the user can arbitrarily define subaccounts (in this example "Work:PrimaryJob:HolidayAllowance").
Although I see your point in wanting clarity, if the format supports arbitrary subaccounts, you can use the tool itself to limiting the number of subaccounts to show (e.g. with 1 you would only see the accumulated amount in all accounts in the "Income:Work" hierarchy). This still fits your use case for clarity, but allows other users to expand the budgeting tool to their needs.