My reason for using .csv over .ofx is simply familiarity and ease of starting up.
I have no experience with ofx and thought the learning curve would be much steeper, and I already feel like I'm drowning a bit as a layperson. I know it may seem like that, especially given ofx is not a human readable format. But might I suggest giving that a shot first, and you might be pleasantly surprised. Because there is nothing to do, no importer to write, since it is a machine format with an official spec, unlike csv. The learning curve should be close to zero. There are other benefits <https://reds-rants.netlify.app/personal-finance/a-word-about-input-formats-use-ofx-when-you-can/> too. I'll look into the csvreader changes you mentioned to try making a replacement for prepare_raw_columns() and also look further into ofx. If I were you, I’d definitely spend five minutes with ofx first. And reds-importers ships with ofx-summarize which you can use to peek inside and poke around an ofx file, which makes it a lot less opaque and easy on a layperson. Thanks for the help here and confirming I'm doing alright, and also thank you for maintaining it! Happy to, and glad its helpful! -- 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/c0471f5c-579e-4ec7-998c-c15b7a46bfa7n%40googlegroups.com.
