After playing with OFX a bit, I realized there are some things I don't like about it. As a reminder, I am coming from CSV import. Maybe these are particular to my bank implementation or not, I don't know; but here they are:
1. No separate transaction and posting dates like I was getting from CSV. Not a huge deal but sort of annoying. 2. The combined narrative field is obnoxious. Often lengthy, all caps, redundant, and full of meaningless (to me) numbers, etc... This is by far the bigger issue. Not unique to OFX but it seems even worse here than CSV was. 3. I am sure some others I am forgetting. But #2, above, is enough all by itself... As I am essentially re-starting from scratch (yet again), I have been really re-thinking my approach the last few days, questioning some assumptions, etc. And at this point I might finally be having some sort of epiphany regarding the more "manual" approach which has always been advocated by Martin, and that I thought I wanted to get away from in my OP. As embarrassing as this may be to admit after essentially making a thread completely in the other direction, I think I need to come clean for the benefit of posterity and anyone following along at home. I won't bore everyone with a point by point list of all the reasons why the "manual" approach is better, but suffice it to say there are many. Anyway I already been toying around with a workflow that begins with taking a photo of my receipts, which I will detail in another post to follow as I think it is a novel approach that might be interesting to others and so far represents my current thinking on the topic after a number of iterations. Cheers, TRS-80 -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/658a75a1e0dbfbb6a20fe5f1d87367a5%40isnotmyreal.name.