A list of things I’d really want to add, beyond fortifying what’s already there:
A generic, configurable CSV importer which you can instantiate. I plan to play with this a bit and build a sniffer that could automatically figure out the role of each column.
A hook to allow you to register a callback for post-processing transactions that works across all importers.
Hi Jonathan,
Q1
I would say whenever you have both (or more) sides of a
transactions then it's the best to import all legs. The thing is
that in most cases you don't have them. On thing that I also do
quite often is, that if I can import both sides of a transaction
form two different sources (e.g. two different banks), then I use
the transaction ids of each bank to add them to the same
transaction, so I know that I have it imported from both sides.
Q2
Not sure if you've come across smart importer https://github.com/beancount/smart_importer, this is a wrapper around your importer that uses existing transactions to guess what the missing other leg could be. For me this works extremely well.
I use it together with the web ui fava https://github.com/beancount/fava
when you then run an importer you get basically the list of all your transactions and you can still modify if the smart importer guess wrong.
What I also started doing more and more (and also works quite nicely), is to actually not even have a file to import but instead directly use an available api (e.g. truelayer, revolut, transferwise, interactive brokers, ...), you can see some examples in my beancounttools https://github.com/tarioch/beancounttools
Q3
There were some enhancements done for hooks: https://github.com/beancount/beancount/issues/458
Regards,
Patrick
--
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 beancount+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/b2b52ac6-b019-4375-adcb-e3f7e6ab0c3bo%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/10207a15-f6f1-d6d6-994c-33e9520e2c83%40ch.tario.org.
To unsubscribe from this group and stop receiving emails from it, send an email to bean...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/b2b52ac6-b019-4375-adcb-e3f7e6ab0c3bo%40googlegroups.com.
--
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 bean...@googlegroups.com.