One of the things that was never done is to specify deduplicating by import source, which would make a lot of sense. Some institutions, e.g. Amex, have really nice unique ids on each transaction that can be used to dedup exactly (if preserved). Some don't. The heuristics I'm using today are imperfect... this needs improvement.
On Tue, Jul 18, 2023 at 6:22 AM Eric Altendorf <[email protected]> wrote: > I see hooks for dup deduction on importers, but the doc comments don't > make it clear how those functions are used. Poking around the code, it > appears that these are only run to dedup items within a single import. > > Is there any functionality to automatically match up legs of a transaction > that come from different importers, e.g., a transfer from one account to > another? > > thanks, > ericc > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/beancount/CAFXPr0vp0MtWcDr0ueMuvXFREO5G1oTGC0UvD%2BRXD%2BdbLG9D%3Dg%40mail.gmail.com > <https://groups.google.com/d/msgid/beancount/CAFXPr0vp0MtWcDr0ueMuvXFREO5G1oTGC0UvD%2BRXD%2BdbLG9D%3Dg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhM2Sexk%3D%3DZ5BQQxK67L9Xbx%2BFAE4%3D-mz9jO%2BjNSPYnJow%40mail.gmail.com.
