Re: double-entry bookkeeping unneeded?
- From: Doc O'Leary <droleary.usenet@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 28 Dec 2006 05:52:54 -0600
In article <5KydnRcGr5oRUA_YnZ2dnUVZ_tadnZ2d@xxxxxxxxxxxxxxxx>,
Thomas Gagne <tgagne@xxxxxxxxxxxxxxxxxx> wrote:
GAAP highly recommends double-entry book keeping. Even in practice, it
is a good tool for financial OLTP systems to make sure nothing is
accidentally recorded to the system that doesn't balance. After all, we
don't want someone increasing their account balance if there wasn't a
source of funds involved, would we?
The question is more whether or not it really makes sense to say this is
correct:
John -5
Bill +5
and this is not:
John Bill 5
The circumstances that make double-entry best practices doesn't
necessarily apply when we have non-physical records that computers can
cross-reference with ease.
--
My personal UDP list: 127.0.0.1, 4ax.com, buzzardnews.com, googlegroups.com,
heapnode.com, localhost, x-privat.org
.
- Follow-Ups:
- Re: double-entry bookkeeping unneeded?
- From: Thomas Gagne
- Re: double-entry bookkeeping unneeded?
- References:
- Re: double-entry bookkeeping unneeded?
- From: Thomas Gagne
- Re: double-entry bookkeeping unneeded?
- From: topmind
- Re: double-entry bookkeeping unneeded?
- From: Thomas Gagne
- Re: double-entry bookkeeping unneeded?
- Prev by Date: use case <<include>> vs. <<generalize>>
- Next by Date: Re: Databases as objects
- Previous by thread: Re: double-entry bookkeeping unneeded?
- Next by thread: Re: double-entry bookkeeping unneeded?
- Index(es):