On 4 October 2012 01:27, Toby Gee <[email protected]> wrote: > 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. > Not with icsv2ledger currently.
> - 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. > Yes but icsv2ledger doesn't do anything with these hashes. I presume the idea was to run ledger looking for transactions tagged with the hash, and if there is one then icsv2ledger should ignore the transaction. Patches welcome. > 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? Implement the above code and add it to icsv2ledger (if that's the tool you wish to continue to use), otherwise it has to be a manual process, or switch to another tool.
