Issue #185: Make duplicate detection configureable (blais/beancount)
85 views
Skip to first unread message
Jakob Schnitzer
Aug 16, 2017, 1:12:39 PM8/16/17
to bean...@googlegroups.com
New issue 185: Make duplicate detection configureable
https://bitbucket.org/blais/beancount/issues/185/make-duplicate-detection-configureable
Jakob Schnitzer:
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`.
https://bitbucket.org/blais/beancount/issues/185/make-duplicate-detection-configureable
Jakob Schnitzer:
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`.
Reply all
Reply to author
Forward
0 new messages