Hello, as far as I know, the builtin duplicate detection of beancount is not to prevent transactions imported twice (for that I built my own hash based duplicate checker), but to detect duplicates when paying from of my account to another one and import both transactions.
I have this existing transaction (all transactions stripped of meta data): 2019-04-01 * "Florian Lindner" "Sparen auf Tagesgeld" Assets:Giro -200.00 EUR Assets:Tagesgeld Now I try to import the statements from the Tagesgeld account using bean-extract -e main.beancount bc.import tagesgeld.csv main.beancount is the main file, which includes the existing transactions. The import generates the transaction: 2019-04-01 * "Florian Lindner" "Sparen auf Tagesgeld" Assets:Tagesgeld 200.00 EUR Expenses:Unknown shouldn't that transaction be caught by the beancount internal duplicate checker and be commented out? I tried to understand the SimilarityComparator, but wasn't quite sure if I got it correctly. Is there a description of the scheme? Thanks, Florian -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/d57ec4a1-36a0-8036-5460-d45cdf961523%40xgm.de. For more options, visit https://groups.google.com/d/optout.
