Using accounts receivable for your friends paying you back is the GAAP solution, so it's what you probably want to do over time. That's how I track my roommates contributions to rent and utilities.
Posting dates with credit cards though, you would essentially charge the initial expense to Liabilities:Bank:Credit-Card:Unposted, then transfer to Liabilities:Bank:Credit-Card:Posted the same day or a few days later. That's a lot of extra effort. This is where you gotta remember that bookkeeping is something you do because the numbers you get are useful, and there's (usually) nothing stopping you from making simplifying assumptions. In this case, what I do is charge the expense to Liabilities:Bank:Credit-Card on the transaction date and just assume that "posting" happens eventually. You can do whatever you want here though. This is where accounting becomes more of an art and less of a science. I've even heard of people who don't import their credit card statements and just record the payments from their bank accounts as expenses. That's pretty extreme because you lose the ability to categorize your expenses and you lose the knowledge of when the dollars were spent, but so is insisting on modeling every finicky nuance of every transaction. Sincerely, Timothy Jesionowski On Wed, Aug 20, 2025, 12:02 PM Yogesh Thambidurai <[email protected]> wrote: > 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 [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/beancount/3bf5a7d9-0e8a-4168-a1dd-a49f9f87ccc5n%40googlegroups.com > <https://groups.google.com/d/msgid/beancount/3bf5a7d9-0e8a-4168-a1dd-a49f9f87ccc5n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 visit https://groups.google.com/d/msgid/beancount/CAOVsoWQrOdwzpk9%2BaQJ%3DDGa5Q9kpxxRp5dZnECFVfh1JYqeiWQ%40mail.gmail.com.
