Sorry - I wrote this two days ago and it's been held up in moderation, I guess.
Since then I tried icsv2ledger, and managed to do most of the below (I'm sure csv2ledger can also do it, of course), so I now have two slightly different questions, one hopefully almost trivial. - is there an easy way in all of this (perhaps in Ledger itself?) to change the sign of all of the transactions for some account? One of my credit cards uses the opposite sign convention to all my other accounts. - how do people deal with avoiding duplicates? Several of these importing options produce MD5 hashes from the original line in the csv file, which should presumably make this straightforward. With my new icsv2ledger setup, each account now produces a ledger file, and I then manually copy it into my main accounts file. Of course, I could write a script to append it to the main accounts file, but is there a better way to import the transactions, avoiding any duplicates, to deal with csv files with overlapping date ranges? On 1 Oct 2012, at 11:01, Toby Gee <[email protected]> wrote: > > > So - is there a way to do this, either by the importing program analysing the > accounts.dat file, or by manually setting up some rules for converting from > payee to liability? > > I'm wondering if CSV2Ledger can do this, based on the above remark: > > "Dynamic renaming based on payee, account matching, even file matching using > a YAML format." > > However I'm not sure how this works in practice - do I just need to read the > comments in the perl file, learn what YAML is etc? >
