[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Thoughts on Voiding Invoices
- Subject: Re: Thoughts on Voiding Invoices
- From: "Chris Travers" <..hidden..>
- Date: Mon, 25 Sep 2006 17:49:23 -0700
On 9/25/06, David Tangye <..hidden..> wrote:
> Most of this argument is about this aspect. I.e. if you void an
> invoice because it was never valid, your data should be to a state as
> if that invoice was never issued in the first place. This means that
> items that are of comparable cost and revenue are rolled up into the
> earlier transactions and so forth. Hence the last unallocated cost
> rule (items of comparable cost and revenue are generally treated as
> bulk items according to this system for reasons I outlined in a
> previous post).
Agreed. A good DBMS like postgres can handle all this using triggers.
its actually very simple SQL in a well-designed database.
Except that by doing so you compromise your audit trail. You want to
have as few transactions as possible to bring the data into a
consistant state. Once you start messing with things after they are
posted, I start to get very nervous...