Make duplicate detection configureable

Issue #185 new
Jakob Schnitzer
created an issue

I'm using Beancount's import mechanism to import the transaction of my main accounts (that are provided as CSV files by my bank). This works quite well in general and is really a step up from doing it all by hand.

Most times duplicates aren't a problem but sometimes I already typed out some transactions by hand that I'm about to import. Since my importer doesn't automatically assign account (which I do by hand on Fava's import page), these don't get recognized as duplicates as the check for duplicates seems to be quite strict.

In my case, the "perfect" duplicate check would only check the amount posted to the checking account that I'm importing the transactions for. So it would be nice if the duplicate check could be configured (and if a "check only amount posted to a single account" would be shipped with Beancount).

I could implement this, if you agree that it would be a useful addition. I would probably add a duplicate_check(entry1, entry2) to importer.ImporterProtocol.

Comments (2)

  1. Adam Gibbins

    I'd certain gain value from this. The duplicate detection generates large amounts of false positives for me, I un-duplicate as part of my import process, so at minimum I'd just like to turn it off. I attach a lot of metadata to my transactions, I've a very good bank that gives me lots of info -- including their own unique transaction ID. So I've a absolute authoritative duplicate source, it'd be nice to utilise that.

  2. Log in to comment