hledger-flow VS beancount

Been using hledger & friends for a few days now:

`2008-01-01 Opening Balance`

hledger-flow is my BFF for managing this: https://github.com/apauley/hledger-flow

I use hledger-flow [1]. It's an opinionated way of importing csvs into the hledger format. Works really well for me, just export the csvs, write a mapping and you are good to go.

It supports preprocessing the csvs if you need to clean the data or compute some new fields which is really powerful. Once you are up and running it only needs some minor updates each month to map unidentifiable transactions I can do this in under an hour these days.

[1] https://github.com/apauley/hledger-flow

I use https://github.com/apauley/hledger-flow to manage the importing/parsing. I have 20 various accounts and after a while it was just too much effort rolling my own solution.

Have you had a look into plain text accounting like e.g. https://beancount.github.io/ ?

Also written in Python, loads of tooling around it. Might be even good to “just” as the database.

[1] https://plaintextaccounting.org [2] https://ledger-cli.org [3] https://beancount.github.io

I used Beancount + Fava for a web UI for years. It stores everything in plaintext files, but the downside is you either have to manually enter everything or probably write a script to import csv/qfx from your bank(s).

beancount -> https://beancount.github.io/

The beancount documentation has some good background material, and the concepts apply to ledger as well.

I track my personal finances using beancount. I have a plugin that I wrote for myself, which in beancount is a python module that is installed in the same python environment as beancount is.