Hi Russell

I have seen such odd principles being used in another application but I would like to disagree. I have not read the full thread so I may be repeating but I think this is not the right way to go about. What is credit is the payment and that is the document / record that should be showing the balance and the remaining of the payment is what has to be applied to another invoice.

Invoice #1 1000/-
Payment #1 1250/- (adjust 1000/- against Invoice #1)
Invoice #2 1750/- (now allow the system to display the Payment #1 1250-1000 = 250/- and adjust against Invoice #2)
Payment #2 1000/- (adjust 1000/- against Invoice #2)
Payment #3 500/- (adjust 500/- fully against Invoice #2)
so on...

Hope it helps. I would suggest you think of these as documents, like paper documents they cannot change beyond what they are.

>While converting a system for a client, I'm running into problems with the way they approach things. One is simply the age-old "we've always done it that way" problem. Something more specific is their desire to have an overpayment on an invoice make the invoice balance go negative, effectively making it an open credit that can later be applied against another invoice. So you have a situation where it's an invoice one day, a credit the next. One day you're getting a payment against it and the next you're using it as a payment to pay something else. To me, this is the wrong way to go about it. I have the system never letting a balance fall below zero and generating a credit invoice for the overpayment amount. Then the credit invoice can be used later to apply against another invoice. This causes some issues for them, though I'm going to address them. Anyone have any thoughts on these two appoaches?
>
>Russell Campbell