I should probably learn what running a report is 😅
I think your second suggestion (running the report on the internal abstraction / on the project, rather than the external structure / the account) would be easier to swing simply because when I'm ingesting data from my bank account (e.g. for the example vendor payment above) the account the statement / data is related to is
Assets:MyBank:Checking, not broken down by project.
(ty by the way, I'll check this out!)
project: MyProjectAor whatever (I can't tell if this would get super tedious, or if this is simply the intention of metadata... I truly truly wish I could use #tags since it seems the fava interface treats tags as a first class piece of metadata in its UX)
@gary I am storing invoices alongside my ledger; do you know if it's possible to maintain a document structure that doesn't mirror accounts directly (e.g. if I track vendor using the Payee model)? With sub-accounts I had each invoice in a
./Liabilities/AccountsPayable/VendorNameHere which aligned with the account. Fava seemed opinionated about that file structure, but I'm wondering if maybe I'm not so locked in.
(or, alternatively maybe I keep the AP sub-accounts but ditch the expense sub-accounts. food for thought.)
I know I'm saying thanks a lot but why stop now: thank you so much for the advice
plugin "fava.plugins.link_documents"in my ledger (btw what is the "noun" for a beancount document? is it ledger? recordset?)
P 2022-01-01 A 3C 2022-01-01 (a) 1A @ 2B comment $ hledger bal -N 1A a $ hledger bal -N -B 2B a $ hledger bal -N -V 3C a