DBA already offers the ability to remove deposits from statements.  We were hoping that the AR-E could be changed to allow overpayments to be excluded from statements, in addition to deposits.  We do not want credits to show on statements.
 
This would save us oodles of time, because now we have to reprint every invoice and stamp it "Past Due" for statements with credits.

1st.  Management can make a rule that if an overpayment exsits for a given period of time unclaimed, that it is written off or contact the customer to use the overpayment.
 
2nd. We need credits to appear on customer statements because they do not always represent a customer overpayment.  Many times a customer will take a debit for product that is returned for repair.  We issue a credit to that customer upon receipt of product for repair.  Or we may issue a price adjustment to a customer which results in a credit.  I don't know how DBA/EVO makes a distinction between types of "credit" - an overpayment versus a credit memo?

I guess every company has their own way of doing things, and I'm not trying to change the way you do it.
 
 
Quote from lmk223a   on 07/15/05 at 04:20:37:

But as long as it isn't taken, it really is a credit and should be shown as one. Once you write it off and reconcile it, it will be gone.
 
 
Quote from lmk223a   on 07/15/05 at 04:20:37:

This is a bit hazy to me. I don't know all the ins and outs of your business or product, and maybe that's the way you have to do it. But it seems that there ought to be a better way.
 
 
Quote from lmk223a   on 07/15/05 at 04:20:37:

Which really is a credit, no?
 
As far as having to pay out for credits, is there any reason why you couldn't have as part of your credit agreement that credits are on account only, not cash?

Wildco,
 
Sorry, as a consultant and lon-time business analyst I have to agree with David.  A credit is a credit is a credit. You should change your business process and rules to match accounting norms.