On Mon, 01 May 2000, you wrote:
> The control is quite worthless, in all but one case, as it is _generally_
> going to be the case that GnuCash is _loosely_ tracking what is happening
> in someone's bank account.
>
> By loosely, I mean that GnuCash is not likely to be the authoritative
> source of information on it.
>
> Discrepancies would include:
> -> I enter a credit card transaction where I bought something on
> April 25th. But it didn't get posted to the account until the 29th,
> because the store was a bit slow in submitting slips.
> -> I issue a cheque on March 15th, which goes in the mail on the 16th,
> arrives at the destination on the 20th, where it sits in the mailbox
> for 3 days, sits on someone's desk for 2 weeks, gets deposited to
> _their_ account April 13th, and then doesn't clear my account until
> April 25th. What date do we put on _that_?
One possibility is to allow different dates on the JEs that make up the
transaction. The default would be to use the same date on each JE within the
transaction. The ordering would then be to the resolution of the "date" entry.
> The exception to this would be if you have an accounts receivable
> account, and intend to charge interest based on daily balances. It
> may be necessary to have an unambiguous ordering of this, particularly
> if the rate depends somehow on minimum/maximum balances. I suggest
> that GnuCash Probably Doesn't Want To Go There...
Daily balances should not depend on the ordering of transactions.
You are correct that "ordering" is important if you wish to base decisions on
the "running" balance. However, I agree that decisions made after the fact
should not use gnucash running balances for that purpose. It is still
possible to generate the decision based on the daily ending balance which
does not depend upon the ordering of entries within that day.
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]