* [email protected] <[email protected]> [2021-05-15 03:33]: > 1. Push as many rules into each importer.
I wouldn't put the rules into each importer. I'd keep each importer focussed on producing a basic transaction. I'd then have a second stage importer which takes those transactions and amends them. This way you don't need to replicate similar logic in each importer. > For example, if $-amount > equals = $2000 and/or description is "payment to ABC apts" then add label > Expense:Rent. I have an importer that does something like that. There are a number of similar "rules-based" importers available. I was planning on sending an email with an overview of each in the hope that we can collaboratively work/agree on *one* solution, but I won't have time in the next few weeks. I can make my solution available with some examples if that'd be useful, though. > I probably have 1500 bank transactions to work through and 3000 > credit card transactions so trying figure out how best to get this > all done and done quickly. I can see that as I do this regularly > 1/month I can get this down to 5-10 minutes with scripts to fetch > ofx files, script to call bean-extract, etc. > > My main question is what should I do now with the historical data to > import? You can always create opening balances for a specific point in time and go back later and add more transactions. -- Martin Michlmayr https://www.cyrius.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/YJ%2Bzp5lBkPCEvzgW%40jirafa.cyrius.com.
