Re: importers and get going

2021-11-12 Thread Bman Q
Eric hi, did you end up pushing your project on github? On Thursday, June 25, 2020 at 11:32:28 AM UTC-4 er...@ericglanz.com wrote: > Jonathan, > > Are you looking to only import investment account information, or > bank/credit card transactions as well? If it's the latter, I've built a > util

Re: importers and get going

2020-06-26 Thread Red S
FYI, I have importers for banks and credit cards that support ofx, based on my beancount_reds_importers library. I'm happy to add that to my python package that you're using if there's interest. I wrap it with smart importer, which is very well designed and written, and gets it right well over

Re: importers and get going

2020-06-25 Thread Jonathan Goldman
Thanks this is very helpful. I was not aware of the smart importer and will try it out. And I’ll check out beancounttools. Thanks! On Thu, 25 Jun 2020 at 5:41 PM, 'Patrick Ruckstuhl' via Beancount < beancount@googlegroups.com> wrote: > Hi Jonathan, > > Q1 > > I would say whenever you have both (o

Re: importers and get going

2020-06-25 Thread er...@ericglanz.com
Jonathan, Are you looking to only import investment account information, or bank/credit card transactions as well? If it's the latter, I've built a utility that does the following: - Reads a config file containing accounts to process - For each account, use ofxtools

Re: importers and get going

2020-06-24 Thread 'Patrick Ruckstuhl' via Beancount
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