3 ms·
Same applies for bookkeeping. Though my .xls will probably outlive most applications, I'm certain that the csv version is readable decades from now. CSV is a po
by berkes 5y ago
Same applies for bookkeeping. Though my .xls will probably outlive most applications, I'm certain that the csv version is readable decades from now. CSV is a poor format, so I'm using a plain text ledger [0] (specifically: the beancount[1] dialect).
I'm quite certain that no webbased SAAS accounting tool will be around in decades. But I'm certain my (git sourced) foo.ledger files are readable and parseable for ages. And if worst comes, they are human readable, so I could even just copy it over, or parse it, manually.
[0] https://plaintextaccounting.org/ https://plaintextaccounting.org/
[1] https://github.com/beancount/ https://github.com/beancount/
FWIW: I chose the beancount dialect over the simpler hledger/ledger format because of the additional support for investments/currencies/assets.
- bstpierre 5y agoYes! I came here to specifically mention plaintext accounting I'm also a beancount user. Having all of my data in plain text allowed me to write extra tooling so that I can generate higher-level reports than what beancount has built-in. (budgeting, cash flow, planning/savings, etc) That tooling also has much faster parsing than beancount. Not a knock against beancount, just proving out the point about not being locked in to a particular binary implementation.