Re: double-entry bookkeeping unneeded?
- From: "topmind" <topmind@xxxxxxxxxxxxxxxx>
- Date: 28 Dec 2006 19:57:45 -0800
JXStern wrote:
On 28 Dec 2006 15:50:30 -0800, "topmind" <topmind@xxxxxxxxxxxxxxxx>
wrote:
I'm anxious to see how that approach implements a single $100 payment
with $98 to interest and $2 to principle.
That is a combination of "transactions", not one. I am not dictating
the "splitter" allocation interface/tool. I am only saying how an
atomic "transaction word" looks like inside the accounting system
(database).
You'd be well advised to put the total of these offsetting entries
inside one database transaction.
Agreed. Saving the total of the "group" wouldn't hurt either.
J.
-T-
.
- 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?
- From: topmind
- 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?
- From: topmind
- Re: double-entry bookkeeping unneeded?
- From: JXStern
- Re: double-entry bookkeeping unneeded?
- Prev by Date: Re: double-entry bookkeeping unneeded?
- 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):