Re: Booking date vs Value/Purchase/Trade date

Particularly for debit/credit card accounts, t really doesn't matter at all in my decade+ long experience, as long as you are consistent. The only related issue is how to date your balance assertions. Here is a thread and here

Re: Booking date vs Value/Purchase/Trade date

Thank you everyone for responses. Just to clarify a little, I am not interested here in the "transfer" usecase which can be solved with limbo account very cleanly as mentioned here and there is indeed a lot of discussions on this topic (I think it would be useful to collect all the information

Re: Booking date vs Value/Purchase/Trade date

This is a known issue, see the settlement dates proposal, is being handled in the c++ rewrite, see v3 design doc. Also lots of history on the mailing list. Currently you either fudge the dates or skip the occasional balance assertion that doesn't want to cooperate. It's unsatisfying but I've been

Re: Booking date vs Value/Purchase/Trade date

This probably varies by country. I'm familiar with US accounting, which typically involves two dates: trade date, and settlement date. In my experience, consistency matters much more than which one you use. Exception: folks who perform advance investing may have more specific requirements. FWIW

Booking date vs Value/Purchase/Trade date

Hello everyone, I am still pretty new to beancount (I started my adventure around a month ago) and I am still tuning my importers and my ledger. When writing importers for my banks, I realized that they often provide multiple dates for one transaction, e.g. "booking date" and "purchase date"),