blais
commented
5 years ago Original comment by Johannes Harms (Bitbucket: johannesjh, GitHub: johannesjh).
bean-extract runs all found (and supported) documents through their importer's extract method in one call.
Not necessarily. It is possible to run bean-extract on just a single file, e.g., on ~/Downloads/data.csv instead of on ~/Downloads
I transfer money from one bank account to another, and I download the CSVs from both banks. Now bean-extract will find both sides of this transaction, but it can't detect them as duplicates.
Two workarounds:
-
First extract data from just one account and add the extracted transactions to your existing data. Then call bean-extract again to extract data from the other account. Bean-extract is then able to find the duplicates. (Note: Fava's web GUI also guides you to import one file after the other, instead of all files at once).
-
Use transfer accounts if you transfer money between two of your own accounts. This eliminates duplicates if you happen to import transactions from both accounts. For example:
#!beancount
; While importing transactions from account A:
; If you encounter a transaction coming from or going to another account of yours,
; then use a transfer account in the second posting, like this:
2018-12-28 * "From account A to account B"
Assets:Bank:A -100 EUR
Assets:Transfer
; While importing transactions from account B:
; If you encounter a transaction coming from or going to another account of yours,
; then use a transfer account in the second posting, like this:
2018-12-30 * "From account A to account B"
Assets:Bank:B 100 EUR
Assets:Transfer
dnicolodi
Original report by Christoph Sarnowski (Bitbucket: csarn, GitHub: csarn).
I'm writing a couple of importers for personal use, and I am missing this feature.
Rationale: bean-extract runs all found (and supported) documents through their importer's extract method in one call. It also has a mechanism to flag duplicate transactions, but only if an existing beancount file is given. Duplicate transactions happen close to each other in time, so it will be very common that both parts of a duplication will be imported at the same time. Imagine I transfer money from one bank account to another, and I download the CSVs from both banks. Now bean-extract will find both sides of this transaction, but it can't detect them as duplicates.
So I would like to see bean-extract run the importer for one file, append the transactions to the list of existing entries, and then pass this updated list to the next importer run.
In case that this behavior is not universally useful, I'd suggest to add a command line switch to bean-extract to enable this.
Any comments or suggestions? Would you accept this feature?