Hi All, I'm getting started using bean count and something that's throwing me off is keeping track of transactions over multiple days.
An example might be dinner with a group of friends. On the day of, I might put my card down to pay. Over the next 1-2 days, my credit card would post, I'd receive bonus points, and my friends might send me a Zelle with their payments. This process would span 4-5 days. Ideally, the sum of this process would come out to zero and I could verify this with bean count, ensuring that all money is accounted for. I could also tag each posting with the actual date it happened, so I can double check with my printed statements. My issue with bean count as I've learned it so far is that transactions are limited to single days. I either need to sacrifice point-in-time accuracy to record all postings on a single day, or sacrifice easy verifiability and recording postings as separate transactions. Right now, I'm going with option two and linking together the separate transactions, as the docs seem to suggest <https://beancount.github.io/docs/beancount_language_syntax.html#links>. This is working okay right now, but I'm having to go through my links and manually verify them. I did find this proposal <https://beancount.github.io/docs/settlement_dates_in_beancount.html> for settlement dates, which would seem to be the solution I'm looking for. However, it's dated back 10 years and I don't think it's been actioned upon. Does anyone have advice to share on accounting for these drawn out transactions? Thanks, Yogesh -- 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 visit https://groups.google.com/d/msgid/beancount/3bf5a7d9-0e8a-4168-a1dd-a49f9f87ccc5n%40googlegroups.com.
