hledger

| tail +2 | hledger -f- -I print unknown' and tweak rules until there are no unknowns, before importing. For the other - I guess I have a similar answer - if you're not certain of your rules, preview the conversion and tweak them, before finalising it. > This process is much faster in a spreadsheet application. IMHO the journal format of hledger and other plaintext accounts apps is too verbose. You can keep your data in CSV/TSV instead of journal. This could be better for spreadsheet interop. I think a more compact, but still readable journal format would be interesting (something between CSV and current journal format). I agree some things are much easier in a spreadsheet (and also, vice versa). > it would be a great relief if someone started a Github repository with expense texts used when you e.g. pay at Carrefour in Italy or Walmart in the USA with your debit card. People could submit those descriptions from the CSV exports of their bank accounts. Please do, I would love to see it! However, wouldn't it be a really huge list of text patterns/regexps, with 0.1% of them useful to any one person ? Perhaps region-specific collections could work. https://github.com/simonmichael/hledger/tree/master/examples... is hledger's collection of CSV rules; these cover the basics of CSV conversion, but not the expense categorising. > Another annoyance in Europe is that there is no API connection for open source apps to bank account statements, you always rely on manual CSV exports. Ha! It's not better in the US at least (except, by giving up your bank credentials to third parties). We are usually envying your APIs over there.

t.")

ld transform your data to a plain text accounting format, with quantities. Eg, make it TSV: $ perl -pe '$c=0; $c++ while $c < 2 && s/ /\t/' a.dat > c.tsv $ cat c.tsv 2020-05-28 18:41 Eat Pizza 2020-05-29 09:00 Slept with the window open 2020-05-29 09:00 Headaches and use hledger CSV conversion rules to customise and enrich it: $ cat c.tsv.rules fields date, time, description # save the time as a tag comment time:%time # count each item as one "event" by default account1 (events) amount1 1 # special cases if pizza account1 (food) amount1 200 cal Now you have a (single entry) accounting journal: $ hledger -f c.tsv print 2020-05-28 Eat Pizza ; time:18:41 (food) 200 cal 2020-05-29 Slept with the window open ; time:09:00 (events) 1 2020-05-29 Headaches ; time:09:00 (events) 1 Allowing quantity reports: $ hledger -f c.tsv balance -MATS cur:cal Balance changes in 2020-05: || May Total Average ======++=========================== food || 200 cal 200 cal 200 cal ------++--------------------------- || 200 cal 200 cal 200 cal $ hledger -f c.tsv activity -D desc:headache 2020-05-28 2020-05-29 * $ hledger-bar -v -f c.tsv cur:cal 2020-05 200 ++ $ hledger-ui --all -f c.tsv # explore with a TUI More at https://github.com/simonmichael/hledger/tree/master/examples...

above) https://github.com/simplex-chat/simplex-chat - secure messaging platform https://www.libhunt.com/l/haskell - more projects...