I'm currently re-starting using beancount for 2017, and I'm trying my damnedest to do it the 'beancount way' this time - write beancount.ingest importers, etc. To facilitate the scripting i might be doing soon, i've been seeding my accounts with some metadata. I'd love to see other examples of metadata, and perhaps be a bit inspired :)
currently I have: - account_id: the institution's account number - customer_id: my identification at the institution - pbs_id: the auto-bill-pay ID - provider: A friendly name for a service provider * an electricity company * a phone company * a bank - interest: a decimal (between 0 and 1) representation of an account's interest per year - min_payment (loans only): my minimum required payment I am envisioning a plugin plugging the last two bits of data into a loan amortization calculator, for example. ## Metadata for forecasting I've also been tentatively adding metadata for forecasting and budgeting purposes. - budget (for variable expenses): If an expense is variable in amount, I use this field to keep an eye on my projections - rate (for fixed expenses): If a bill is always the same size, no fuss, no muss. - schedule: monthly, quarterly, biannual, annual. A plugin could conceivably parse these and convert to fava budget syntax. -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/ddbe4583-c622-4739-92df-7f38912d148a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
