On Tue, 23 May 2000, John Hasler wrote:
> Linas writes:
> > But here's the features that no 'ordinary' account has:
> > the ability to compute & display:
> > 'how old (how many days) is joes debt?'
> > 'how old is the average debt?'
> > 'what's teh average a/r balance for the last month?'
>
> 'aging': an essential feature for most business applications. Can't it be
> done with a report?
I think that it should be done as a report. I also think that Linas was
suggesting that creating the mechanisms to generate such reports would be a
good and reasonable project.
> > say joe & bob both borrowed money. One of them paid me back. How do I
> > find out who still owes me money? (short of reading the whole thing by
> > hand, which would be nasty if there are hundreds of debts recorded).
>
> 'Assets:Accounts Receivable:Joe' has a zero balance.
> 'Assets:Accounts Receivable:Bob' does not (and if parent accounts worked
> the way I wish they did, 'Assets:Accounts Receivable' would contain a list
> of the balances of all the customers accounts and it would be easy to pick
> out the non-zero ones).
This brings up a philosophical question. Should we have a separate subaccount
for each "customer". Or is it reasonable to place all the customers into one
account?
