On Wed, Jul 2, 2014 at 9:15 AM, Simon Michael <[email protected]> wrote:
> On 7/1/14 6:16 PM, Martin Blais wrote: > >> On Tue, Jul 1, 2014 at 8:41 PM, Simon Michael >> <[email protected] >> <mailto:[email protected]>> wrote: >> - There can be more than two dates of interest in real-world >> transactions. >> >> Do you have a common real-world use case? >> > > My first example, eg - I made a transfer between banks using online UI > over the weekend, it cleared in one bank a few days later, and in the other > bank a few days after that. That's two dates: the date where the amount was debited from the source bank, and the date the amount was credited to the destination bank. Why do you care about the date you initiated the transfer? That's a comment IMO, not the date you should place your transaction at. > Is HLedger also subject to the "amounts in limbo" problem I describe in >> my doc, or are you splitting the transaction into multiple balancing >> ones as I suggest? >> > > Yes it is. I suspect accountants don't sweat much over this, they just > draw up balance sheets at well-defined times and business activity > naturally slows down around then, or if needed they adjust dates until all > transactions fall into a single accounting period. I doubt this is how it works. Think of a company, that has a ton of different receivables and payables, and tons of such transfers. Surely they have to take it into account, they can't afford to find such a date. In any case, in Beancount I'm able to generate balance sheets and income statements at any point(s) in time, and they need to balance precisely, so I need to deal with the limbo problem for sure. -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
