fava

thonanywhere.com/example-beancount-file/incom...) to check your accounting (with all files listed in the journal by date, with tags and links and other neat features) and still be able to browse documents in your file browser.

at all before aside from earlier attempts of using mint. Beancounts documentation ( https://docs.google.com/document/d/1RaondTJCS_IUPBHFNdT8oqFK... ) is great but is dense and spread out a bit, thankfully their email list ( https://groups.google.com/forum/#!forum/beancount ) is pretty active and helpful. - The ledger file will get big, but it's easier than having multiple files. Use syntax highlighting & more importantly code folding. And no you don't have to be an emacs/vim nerd to do this (i'm using sublime FWIW). - There's migrators from mint/etc. but those aren't perfect because the data from mint isn't always perfect. I went through the exercise of categorizing many transactions from earlier years. It's a masochistic option but really wanted some historical data. Ultimately you'll find yourself refactoring/re-categorizing things over time, and because it's in a git repo you won't be afraid to be ruthless about this. - Writing your own importers is part of the learning curve. You might find some odd ones on github but you ultimately want to write your own - the examples in beancount's source code are a good starting point. You don't have to do it for everything, just the ones that are too unwieldy for tracking manual transactions. - I'm still wrapping my head around how to leverage beancount to function as a budgeting / forecasting tool. Several friends use YNAB (there's also financier.io) instead for those needs.